-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Refactor ItemsLayout handling: dynamic default + virtual view-managed subscriptions v2 #29683
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
base: main
Are you sure you want to change the base?
Refactor ItemsLayout handling: dynamic default + virtual view-managed subscriptions v2 #29683
Conversation
e026d3b
to
8012865
Compare
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
31ae867
to
6573300
Compare
…29683 Co-authored-by: PureWeen <5375137+PureWeen@users.noreply.github.com>
/rebase |
1cf7474
to
380090e
Compare
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
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.
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
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.
looks like this one is failing consistently
CollectionViewWithFallbackVauleShouldUpdateAtRunTime
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
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.
Added samples and tests related with #31071
|
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
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
For more information on the problem and the fix, see: #29638 (comment)
Why this ?
In #29638, we currently call
MapItemsLayout
when properties such asItemSpacing
,Span
, etc., change.This means that any property change within
ItemsLayout
triggers a full layout remap.For example:
When changing the
Span
of aGridItemsLayout
, we can simply update the platform view’sSpan
without re-creating the layout.The problem
It's not always correct to use the same mapper (
MapItemsLayout
) for:ItemsLayout
, andThe solution
This PR introduces a dedicated command mapper to handle property changes within
ItemsLayout
.It separates:
MapItemsLayout
— for when the layout object itself is replaced.Span
,ItemSpacing
, etc.Supersedes #29638 , #29635 , #28675 , #29190 , #28311
Issues Fixed
Fixes #29619
Fixes #27666
Fixes #27667
Fixes #28656
Fixes #29696
Fixes #28023
Fixes #23377
Fixes #31259
Fixes #31071