JS Errors: Remove the content headers from the JS Errors API #3306
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
scruffian
added
Framework
[Status] Needs Review
|
👍 Ready to 🚢 once you add back the condition to only run it in staging! |
scruffian
added
[Status] Ready to Merge
and removed
[Status] Needs Review
… they aren't needed, and covert the error to an object before we pass it to the array
scruffian
force-pushed
the
update/js-errors
branch
from
08cd942
to
041d79c
Compare
scruffian
force-pushed
the
update/js-errors
branch
from
041d79c
to
bd629f0
Compare
scruffian
added a commit
that referenced
this pull request
Feb 16, 2016
JS Errors: Remove the content headers from the JS Errors API
This was referenced Feb 20, 2022
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.
This also converts the error to an object before we pass it to the array.