Share private worksets #165
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
…dling with a warning and a redirect of some sort
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.
Trying to access worksets the user is not authorized to access (such as from a shared link to a private workset, or logging out while working with a private workset), or an invalid workset id have been causing crashes of the frontend for not correctly handling the error type. Now these cases should return an HTTP 400 error, which could be used to create a meaningful error message for users, instead of the generic 500 error which we were getting before. Error logs on the server side should now be a bit more informative too.
Also renamed a few parts of the front-end, and limited public and user worksets from AG to 400 volumes.