-
-
Notifications
You must be signed in to change notification settings - Fork 754
fixing issue with backing field naming and serialization failing #1785
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
AArnott
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@neuecc I'm not familiar with the changed code. Would you mind taking a look?
|
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
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the added explanation. I'll take it.
|
@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. |
Fix for #1776