test972: verify the output without using external tool#9564
Closed
bagder wants to merge 3 commits into
Closed
Conversation
It seems too restrictive to assume and use an external tool to verify the JSON. This now verifies the outut byte per byte. We could consider building a local "JSON verifyer" in a future. Reported-by: Marcel Raad Fixes #9563
bagder
force-pushed
the
bagder/test972-without-exttool
branch
from
7f07858 to
d6c0c2d
Compare
Not used anymore
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.
It seems too restrictive to assume and use an external tool to verify the JSON. This now verifies the outut byte per byte. We could consider building a local "JSON verifyer" in a future.
Reported-by: Marcel Raad
Fixes #9563