Decode forward slash #4
Merged
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.
The formatter was preserving escaped forward slashes (
\/) in JSON strings instead of decoding them to normal forward slashes (/). This caused URLs and file paths to display with escaped slashes, making JSON output harder to read and inconsistent withJSON.stringifybehavior.Fix: Added handling for
\/escape sequences in thescanString()function to decode them to/, matchingJSON.stringifybehavior.Changes
FORWARD_SLASHconstant (character code 47)Before & After Example
Example