Skip to content

Introduce SetterSpecificity.FromUnknown to avoid misuse of FromHandler #30122

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

bhavanesh2001
Copy link
Contributor

@bhavanesh2001 bhavanesh2001 commented Jun 22, 2025

Note

Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!

Description of Change

Adds a new SetterSpecificity.FromUnknown for cases where a value needs to be applied with higher priority but should still be overridable by everything else, including FromHandler.

This addresses current misuse of SetterSpecificity.FromHandler in scenarios that are not actually coming from the platform/handler.
These usages are not handler-driven updates. Overloading FromHandler here undermines its intent and blocks necessary changes (like in #29970) to prevent round-trips in handler-property mappings.

Issues Fixed

Contributes to #29970
Contributes to #22585

@PureWeen
Copy link
Member

/azp run

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@PureWeen PureWeen requested review from StephaneDelcroix and removed request for Aguilex and tj-devel709 June 23, 2025 02:05
@bhavanesh2001
Copy link
Contributor Author

cc @StephaneDelcroix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community ✨ Community Contribution
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants