-
Notifications
You must be signed in to change notification settings - Fork 913
chore: More UI friendly errors #1994
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
352b86a
chore: More UI friendly errors
Emyrk 7f9b66a
chore: Update BE http errors to be ui friendly
Emyrk 46b52d5
chore: More friendly errors as responses
Emyrk 1592d08
Fix typo
Emyrk 6b08a08
Add internal error to the cli
Emyrk 1b3947f
Merge remote-tracking branch 'origin/main' into stevenmasley/ui_errors
Emyrk deb5cf1
Remove empty switch case
Emyrk 5e34b5f
Update coderd/gitsshkey.go
Emyrk f355dff
Update coderd/gitsshkey.go
Emyrk 6566e83
Update coderd/gitsshkey.go
Emyrk fed7b7f
Update coderd/gitsshkey.go
Emyrk 5c4ec92
Update coderd/gitsshkey.go
Emyrk e373a06
Update coderd/httpapi/httpapi.go
Emyrk 73ffa22
Rename "Internal" -> "Detail"
Emyrk 5d59312
Rename "Errors" -> "Validations"
Emyrk a8e78bb
Fix proper captalization
Emyrk ee2f547
Fix typo
Emyrk 4a5d03a
Fix accidental 'detail'
Emyrk 8259e51
Merge remote-tracking branch 'origin/main' into stevenmasley/ui_errors
Emyrk 819f2e1
PR comments addressed
Emyrk 1116f94
Linting changes
Emyrk 102a01f
Fix test error asserts
Emyrk af169f0
Fix test error asserts
Emyrk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: what allowed us to make this change? Does it mean that we no longer send those random
Message
errors on forbidden routes?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vapurrmaid for security reasons all forbidden messages should be identical. If they were different, then the different errors allow the end user to gain information.
There is a line of "security" vs "usability" that we will need to decide on these endpoints. As it's unhelpful by design.