Mercurial > gemma
view client/README.md @ 5351:4b367f7e39b4 extented-report
Added messaging from overview to details.
When the userdetails is open and the state of the toggle for
receiving reports is changed, this change is now progagated
to the details view via props.
The canonical way would have been to use Vue.set on the instance of
currentUser. But this did not work as expected. So this way
via props seems to do the trick.
| author | Thomas Junk <thomas.junk@intevation.de> |
|---|---|
| date | Tue, 22 Jun 2021 12:58:38 +0200 |
| parents | da04fa72cee8 |
| children |
line wrap: on
line source
* Install dependencies * [Yarn](https://yarnpkg.com/) and a compatible nodejs version is needed, see `engines` section in `package.json`. * Install (`xgettext`) tool (e.g. for Debian xgettext (GNU gettext-tools) 0.19.8.1) * Javascript `yarn install` * Extend or overwrite configuration via `.env.local`-file ``` cp .env .env.local ```` Modify `.env.local` according to your needs. * Start Development servers * Javascript Run webpack-dev-server with `yarn serve` Hint: if you want to access the dev-server via a tunnel with hot reload, you'll may need to explicitely set the url the browser has to call with public. Example: ```sh ssh bern@ourdev.intevation.de -L 8180:localhost:8180 yarn serve --port 8180 --public http://localhost:8180 ``` * Build `yarn build` builds the production ready assets to `web` folder. This is what the `../Makefile` will call, which you should use anyway. For a real production use, edit the `title` tag in `public/index.html` to something matching your installation. * Build `yarn build-demo` sets the hg revision as a node env var and builds the production ready assets to `web` folder. * Translation * Extract Messages via `make makemessages` * Translations are converted via `make translations` which is executed automatically with yarn serve/build For more information see [developer documentation](./docs/developer.md) * Tests * Unit tests are started via `yarn test:unit` * e2e tests are started via `yarn test:e2e` Vue cli supports the Chrome selenium driver out of the box If you are interested in using the Firefox variant of the driver see [Vue CLI Plugin Docs](https://github.com/vuejs/vue-cli/tree/dev/packages/%40vue/cli-plugin-e2e-nightwatch) and see also [Nightwatch documentation](http://nightwatchjs.org/gettingstarted#geckodriver)