Setter Specificity

[StephaneDelcroix]

Description

In order to better compute the current values for BindableProperties, we need to keep a list of all values being set, with their Specificity, instead of relying on some heuristics (from style, etc.) and order of application.

The specificity concept is borrowed from CSS, and keeping a list of values with specificity will allow

• finer grained application of value
• more robust unapply of values (think VSM, or Styles)
• better support for HotReload

(Public) API Changes

No public API change

Usage Scenarios

/

Backward Compatibility

This will fix a few existing bugs, so might break apps relying on those bugs or wrong behaviours. We're thinking about walling this behind a feature flag, enabled by default on the new templates, opening the opportunity to include this as a service release of net7

Difficulty

Medium

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.