Add option to disable HTML escaping in strings#6
Open
noise64 wants to merge 1 commit intoTylerBrock:masterfrom
Open
Add option to disable HTML escaping in strings#6noise64 wants to merge 1 commit intoTylerBrock:masterfrom
noise64 wants to merge 1 commit intoTylerBrock:masterfrom
Conversation
|
Could this be merged @TylerBrock ? |
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
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.
Pretty printing strings with HTML unsafe characters (e.g
<) can be quite "unpretty" with the default HTML escaping. This PR adds option to control this.The
RawStringsoption can achieve similar effect, but with this option the output is both pretty and still valid JSON.I kept the original code path using
json.Marshalas before, so the performance with default options should not be affected except for the bool check.