Mercurial > gemma
view client/README.md @ 5348:45b03e8ca47e extented-report
Toggles in user overview and in details section as well established
This commit introduces toggles to change the state for administrative
users to be able to receive the DQL Report.
For quick access there is the possibility to change via overview.
If you want to edit this in the details or if you change the role
of the user to a non administrative, there is the possibility to change
the flag in a fast way.
When the user looses administrative privilege the option is not available
and the according flag is set to "false".
Aside: Changed user.go to resolve inconsitencies in frontend where the
key "reports" was missing due to "omitempty" in marshalling the go objects.
| author | Thomas Junk <thomas.junk@intevation.de> |
|---|---|
| date | Mon, 21 Jun 2021 16:41:39 +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)