fix: return proper JSON from REST API #3606
Closed
Conversation
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
Contributor
Author
|
@vicsn @niklaslong I think this approach is acceptable, it only changes the behaviour for the REST call. |
joske
force-pushed
the
json
branch
3 times, most recently
from
4205e9c to
a28aa20
Compare
Contributor
|
Closing this in favor of #3751. |
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.
Motivation
Some endpoints return just a
Displayimplementation for serializing of aValue. This leads to invalid JSON. See #3361. Note that this approach does preserve order.Filing as draft to solicit feedback.
Test Plan
Tested manually as described in the linked issue.