fixing issue with backing field naming and serialization failing #1785
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
|
I can give some context too. It seems that original intent was to determine if there were more than 1 candidate for property. This would be the case when property is overridden with a "new" keyword. Since it collects members ignoring case, this falsely flags case when backing field matches property name such as myProp/MyProp. |
|
Any chance of somebody taking a look at it? |
AArnott
approved these changes
Mar 31, 2024
|
@AArnott How do I get a hold of package that has this fix merged in? Latest released is 2.5.140? |
|
Watch for 2.5.168 to appear on nuget.org in the next few minutes. |
This was referenced Jul 21, 2025
This was referenced Sep 19, 2025
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.
Fix for #1776