Handle no responseJSON
coming back from POSTs/xhrs
#3273
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.
What does this PR aim to accomplish?:
This resolves issues with frontend JS when the server fails to send a
responseJSON
reply, leaving the frontend hanging in a "loading" state.This also resolve these console errors:
How does this PR accomplish the above?:
We confirm that
responseJSON
exists in the response object before accessing into it.By submitting this pull request, I confirm the following:
git rebase
)