fix: handle separately 401 and 403 api errors in UI #1740
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
for more information, see https://pre-commit.ci
keithCuniah
reviewed
Sep 30, 2022
frascuchon
commented
Sep 30, 2022
keithCuniah
reviewed
Sep 30, 2022
frontend/plugins/vuex-orm-axios.js
Outdated
| type: "warning", | ||
| }); | ||
| break; | ||
| default: | ||
| Notification.dispatch("notify", { | ||
| message: error, | ||
| message: "Error: " + messageDetail.params.detail, |
There was a problem hiding this comment.
Some code smeller recommends to concatenate strings with backtick like so : (backtick)Error: ${messageDetail.params.detail}(backtick)
frascuchon
deleted the
bugfixes/handle-ui-error-when-cannot-delete-dataset
branch
frascuchon
added a commit
that referenced
this pull request
Sep 30, 2022
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270) fix: handle separately 401 and 403 api errors in UI (#1740) Since the changes included in #1713, users without permission trying to delete datasets from UI will hit into a re-login operation. This PR handles separate authentication errors (401) and forbidden errors (403). We should find a better way to handle error codes and info in general.
frascuchon
added a commit
that referenced
this pull request
Oct 3, 2022
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270) fix: handle separately 401 and 403 api errors in UI (#1740) Since the changes included in #1713, users without permission trying to delete datasets from UI will hit into a re-login operation. This PR handles separate authentication errors (401) and forbidden errors (403). We should find a better way to handle error codes and info in general.
frascuchon
added a commit
that referenced
this pull request
Oct 4, 2022
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270) fix: handle separately 401 and 403 api errors in UI (#1740) Since the changes included in #1713, users without permission trying to delete datasets from UI will hit into a re-login operation. This PR handles separate authentication errors (401) and forbidden errors (403). We should find a better way to handle error codes and info in general.
frascuchon
added a commit
that referenced
this pull request
Oct 5, 2022
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270) fix: handle separately 401 and 403 api errors in UI (#1740) Since the changes included in #1713, users without permission trying to delete datasets from UI will hit into a re-login operation. This PR handles separate authentication errors (401) and forbidden errors (403). We should find a better way to handle error codes and info in general.
frascuchon
added a commit
that referenced
this pull request
Oct 5, 2022
…users (#1713) * feat(Datasets): restrict dataset deletion only to creators and super-users * tests: add tests for datasets deletion check * chore: improve deletion error message Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> * Format long strings Co-authored-by: Daniel Vila Suero <daniel@recogn.ai> (cherry picked from commit c5ab270) fix: handle separately 401 and 403 api errors in UI (#1740) Since the changes included in #1713, users without permission trying to delete datasets from UI will hit into a re-login operation. This PR handles separate authentication errors (401) and forbidden errors (403). We should find a better way to handle error codes and info in general.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since the changes included in #1713, users without permission trying to delete datasets from UI will hit into a re-login operation.
This PR handles separate authentication errors (401) and forbidden errors (403).
We should find a better way to handle error codes and info in general.
Refs: #1713