[bug] @Json.Property name not used to match getters/setters/constructors using property name #337
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
now will read the getter/setter methods using the property name if no match if found for the field name
rbygrave
requested changes
Mar 2, 2025
Contributor
rbygrave
left a comment
rbygrave
left a comment
There was a problem hiding this comment.
We haven't got any tests with asserts yet, I think we need to add some that covers the constructor and setter options.
rbygrave
changed the title
rbygrave
approved these changes
Mar 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Now will read the getter/setter methods using the property name if no match if found for the field name.
This was prompted by
