Keep JSON response transformations consistent - #295
Merged
Merged
Conversation
|
Comprehensive JSON transformation with robust structure and big-int handling. 🎯 Quality: 100% Elite · 📦 Size: Medium 🤖 Authorship: Probably agent-written — OpenAI Codex, going by its branch name. Whether a person read it is unknown; coding agents can call the 📈 This month: Your 147th PR — above team average · Averaging Excellent |
Contributor
Author
|
/review |
mariojgt
approved these changes
Sep 28, 2026
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
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.
Keep numeric JSON values aligned between matching and response transformation, while preserving untouched large integer tokens and literal strings.
Validate whole-document JSON before tokenization. Check each text-span rewrite for unchanged keys, containers, and non-string tokens; string values may change. Explicit path transformations retain their existing replacement semantics. An incompatible rewrite uses the existing generic withheld response.
Synthetic tests cover numeric leaves, literal strings, custom masks, transformation ordering, object and array structure, dry-run behaviour, and the Node response path.
Validation: full suite (3,428 passed, 7 skipped), typecheck, build, and unchanged capability and rule contracts.