Sort toolsnaps JSON keys recursively to eliminate noop churn #1816
+1,699
−1,558
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
Toolsnaps now write JSON with consistent alphabetical key ordering at all nesting levels, eliminating diff churn from Go's randomized map iteration.
Why
Toolsnap diffs showed field reordering noise even when schemas hadn't changed. Example from a typical regeneration:
"order": { - "type": "string", - "description": "Sort order", + "description": "Sort order", "enum": ["asc", "desc"] + "type": "string" }What changed
sortJSONKeys()ininternal/toolsnaps/toolsnaps.go: unmarshals and remarshals JSON to leverage Go's built-in alphabetical map key sortingwriteSnap()to sort before writingMCP impact
Prompts tested (tool changes only)
N/A
Security / limits
Tool renaming
Lint & tests
./script/lint./script/testDocs
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.