-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[release/8.0-rc2] Fix options Validation with objects have indexers #92311
[release/8.0-rc2] Fix options Validation with objects have indexers #92311
Conversation
Tagging subscribers to this area: @dotnet/area-extensions-options Issue DetailsBackport of #92309 to release/8.0-rc2 /cc @tarekgh Customer ImpactTestingRiskIMPORTANT: If this backport is for a servicing release, please verify that:
|
@artl93 @ericstj @jeffhandley I am submitting a request to port this fix to RC2. This issue represents a regression that occurred in RC1, and it would be beneficial to include the resolution in RC2. |
@tarekgh backports to RC2 now need to go through Tactics approval, so please send them an email. Also please get a code review sign-off. BTW there was a generalized failure in the RC2 branch for which we just merged a fix, so I updated this branch to ensure we got a clean CI result. |
@ericstj @stephentoub this is a backport of the PR you reviewed #92309. Could you please approve it? |
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.
M2 approved.
Approved by Tactics via email. |
Backport of #92309 to release/8.0-rc2
/cc @tarekgh
Customer Impact
Users who perform options validations using objects containing indexers may encounter exceptions. This issue represents a regression from earlier releases and is a direct result of the changes made to support the new validation attributes, namely
ValidateObjectMembersAttribute
andValidateEnumeratedItemsAttribute
.Testing
Passed the regression tests and added more tests to cover the failing cases.
Risk
Low, this change is highly specific and pertains solely to cases where an object contains an indexer, with no impact on any other aspects of the logic.
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging
, notrelease/X.0
.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.