Repository navigation
Fix broken JSON escape tool link - #456
Open
coderaviverma wants to merge 1 commit into
Open
coderaviverma wants to merge 1 commit into
coderaviverma wants to merge 1 commit into
Conversation
Signed-off-by: Coder Avi Verma <avi.verma8989@hotmail.com>
|
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
1 participant
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 contributor guide's JSON escape link now opens a 404 page. This replaces that destination with a working escape/unescape tool while keeping the existing regex workflow unchanged.
I maintain JSONViewerTool and am affiliated with the replacement. I verified the target returns HTTP 200 and supports both escaping and unescaping JSON string content.
Validation:
git diff --check