Add support for returning pretty JSON response in axum_extra::response::ErasedJson
#662
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
…onse::ErasedJson`
jplatte
approved these changes
Dec 27, 2021
davidpdrsn
reviewed
Dec 27, 2021
davidpdrsn
reviewed
Dec 28, 2021
jplatte
changed the title
axum_extra::response::ErasedJsonaxum_extra::response::ErasedJson
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.
Fixes #657
I can also add a new
PrettyJsonstruct as initially discussed in the above issue,but later seeing the implementation of
ErasedJson, I thought it's better to just implement it there and avoid bloating the project with a third struct with an almost identical implementation toaxum::Jsonandexum_extra::response::ErasedJson.