Commit Graph

8 Commits

Author SHA1 Message Date
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
Simone Gotti
2891b62b6c *: move to tailwind css
I really like it!

TODO: Extract more components
2019-05-21 12:13:21 +02:00
Simone Gotti
789d0f5fcd *: handle api errors
* Use a global error when fetching data
* Use a local error message when calling a mutating api
2019-05-13 16:29:47 +02:00
Simone Gotti
fb3509fc9d login: use fetchRemoteSources 2019-05-06 17:57:52 +02:00
Simone Gotti
19fdb1d08f initial implementation of projectgroups
and related tree based navigation
2019-04-02 18:08:03 +02:00
Simone Gotti
ef5a9c4994 Add user registration 2019-03-29 18:08:54 +01:00
Simone Gotti
b9fb3d6860 update for new api 2019-03-20 13:51:00 +01:00
Simone Gotti
b780e148cc Initial commit 2018-12-09 14:21:20 +01:00