avoid HTML escaping in JSON files #3560
Open
+16
−9
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.
Currently the HTML characters "<" and ">" are escaped in the JSON file micro writes, see here. This makes the
bindings.json
file hard to read: Instead ofone gets
This PR changes this. I'm assuming that the HTML security concern behind the escaping doesn't apply here. For
settings.json
I don't have a strong use case. I just thought it's best to use the same code for both files.