-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Fix for Configuration Binder Source Gen duplicate field names #120135
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
Configuration Binder source generator generates duplicate field names where the same class name is present in different namespaces. Fix #119458
|
Tagging subscribers to this area: @dotnet/area-extensions-configuration |
|
@dotnet-policy-service agree |
|
@tarekgh - please review this. |
|
I have run Please advise if I should include updated Version 0 baselines in my PR. |
src/libraries/Microsoft.Extensions.Configuration.Binder/gen/Parser/Extensions.cs
Show resolved
Hide resolved
NamespaceA name clashes. "SymbolDisplayMiscellaneousOptions.UseSpecialTypes" - is no longer a problem. Added "___" as generic type delimiter to solve A.BC vs AB.c name clashes. Shortened maximum identifier length to slightly improve code readability.
tarekgh
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 @alex-lutsenko!
|
Thank you! |
|
@tarekgh - I do not see my fixes in the latest (10.0.0-rtm.25479.115) for Microsoft.Extensions.Configuration.Binder. Am I missing something? Is it not going to be released in .NET 10? |
No, this is scheduled for .NET 11. Including it in .NET 10 would be risky since the fix hasn’t been released in any preview, and we can’t guarantee that it won’t introduce side effects. |
Configuration Binder Source Generator generates duplicate field names
where the same class name is present in different namespaces.
Fix #119458