Open
Conversation
Signed-off-by: Pecacheu <3608878+Pecacheu@users.noreply.github.com>
Member
|
If the client adds |
Contributor
Author
Ah, good to know. I assume that's a change for stoat.js and not for-web though? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Now ideally the Stoat backend should just not send API errors in HTML format to begin with (but as raw text or JSON, for instance) because it wastes network bandwidth, but hey, stripping it on the frontend also helps in case any HTML-formatted errors from other sources slip through the cracks. Which- if other people's error report screenshots are anything to go by- happens a lot.
Old:
New:
