fix: support json_name with non-alphanumeric characters for all field types #521
Conversation
This file contains 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
stephenh
pushed a commit
that referenced
this pull request
Feb 21, 2022
## [1.106.1](v1.106.0...v1.106.1) (2022-02-21) ### Bug Fixes * support json_name containing hyphen on all field types ([#521](#521)) ([8d9e78e](8d9e78e))
|
🎉 This PR is included in version 1.106.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Use
array[access] syntaxfor all field types with a json_name containing non-alphanumeric characters.Sorry to bother you once more @stephenh 😅.
I missed a few instances where
${jsonName}was still used instead of the safe property accessor.Double checked it now using IDE variable usage, so it should work everywhere now.