agola web ui
Go to file
Simone Gotti 43e860d3c5 auth/data: avoid setting global errors when receiving a 401
If we do a router.push to the login view the previous component will receive
anyway the error and set the global error after the login view is mounted (!!!)
and so the main app will show the global error instead of the login view.

Not sure how to avoid this. As a really ugly workaround just return an empty
response on 401 so the components (since they are currently assumong the
response is always define) will throw an exception and not set the global error.
2019-07-05 13:41:43 +02:00
.agola add agola build config 2019-05-22 17:09:57 +02:00
public *: move to tailwind css 2019-05-21 12:13:21 +02:00
src auth/data: avoid setting global errors when receiving a 401 2019-07-05 13:41:43 +02:00
.dockerignore Initial commit 2018-12-09 14:21:20 +01:00
.gitignore Initial commit 2018-12-09 14:21:20 +01:00
Dockerfile Initial commit 2018-12-09 14:21:20 +01:00
LICENSE Initial commit 2018-12-09 14:21:20 +01:00
README.md Initial commit 2018-12-09 14:21:20 +01:00
babel.config.js Initial commit 2018-12-09 14:21:20 +01:00
jsconfig.json *: move to tailwind css 2019-05-21 12:13:21 +02:00
package-lock.json update dependencies 2019-05-23 16:22:17 +02:00
package.json update dependencies 2019-05-23 16:22:17 +02:00
postcss.config.js *: move to tailwind css 2019-05-21 12:13:21 +02:00
tailwind.js *: move to tailwind css 2019-05-21 12:13:21 +02:00
vue.config.js Initial commit 2018-12-09 14:21:20 +01:00

README.md

agola-web

Project setup

npm install

Compiles and hot-reloads for development

npm run serve

Compiles and minifies for production

npm run build

Run your tests

npm run test

Lints and fixes files

npm run lint

Customize configuration

See Configuration Reference.