[payload] Set status code on error rather than query status #4567
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.
@mistercrunch previously you used to raise an exception if there was no-data, which would then get caught here and thus the non-200 status code would ensure that the error message was reported.
When I removed the exception, and instead set the error message (to ensure consistency with how other query errors were handled) the exception wasn't raised, and the response status code was defined purely on whether the query failed or not rather than also checking the presence of an error.
Note in the future I'll try to take a pass at unifying some of this logic; standardizing payloads, determining when exceptions should/shouldn't be thrown, etc.