Fix wrong string escape in RichText's attrs #439
Closed
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
In RichText's attrs, missing backslash before special characters caused JSON parse error. RHT.Marshal() now inserts escape characters when constructing JSON encoding.
|
|
|
This PR will wait for PR #438 to be completed; RichText test should be modified since |
|
This was merged by #443. |
2 tasks
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.
What this PR does / why we need it:
In RichText's attrs, missing backslash before special characters caused JSON parse error. RHT.Marshal() now inserts escape characters when constructing JSON encoding.
Which issue(s) this PR fixes:
Fixes #437
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation:
Checklist: