Switch all JSON output to PascalCase #298
Open
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
When these were added over the last week, I didn't realize we were already (mostly) using PascalCase throughout our existing JSON output. This changes all of these fields to PascalCase and is not a breaking change because none of these fields existed in JSON output in v2.3.5.
These snake_case and camelCased fields existed in v2.3.5 and are a breaking change to move to PascalCase for v3.0.0. I do not plan on leaving a backcompat field for these.
dan-manges
previously approved these changes
Jan 17, 2026
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.
Many of these were added since our last release so they're not breaking changes.
This commit contains breaking changes: 9096919