test: add canonical JSON whitespace regression#26
Merged
Conversation
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.
Summary
Adds a regression test proving that canonical JSON output is stable across input whitespace differences.
The test parses compact and formatted JSON with the same semantic content and verifies that both produce identical canonical JSON.
Why
DigiEmu Core depends on canonical JSON stability for deterministic hashing.
This protects against formatting drift from spaces, tabs, newlines, pretty-printed JSON, and editor/tool differences.
Test
Added:
TestCanonicalJSONIgnoresInputWhitespaceVerification
go test ./...