Refactor ItemsLayout handling: dynamic default + virtual view-managed subscriptions v2#29683
Refactor ItemsLayout handling: dynamic default + virtual view-managed subscriptions v2#29683bhavanesh2001 wants to merge 35 commits intodotnet:mainfrom
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). |
4cdb6d8 to
dbb3e5d
Compare
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
| [Controls.CarouselView.CurrentItemProperty.PropertyName] = MapCurrentItem | ||
| }; | ||
|
|
||
| //TODO Make this public in .NET10 |
There was a problem hiding this comment.
Ideally we could retarget to the net10.0 branch, and remove this TODOs, but I think not is too late.
|
any updates? |
|
I think we merged a couple of other PRs now to fix some of the things that are happening here, so this one is a bit stale now. Also this one is a bit too big and complicated to just take at once. Probably for a next time its better to have multiple smaller PRs that will make it easier for us to merge. If you still want to take this one over the finish line, please have a look at what is still left to be done and split that into several PRs. Thanks! |
|
Hi @@bhavanesh2001. We have added the "s/pr-needs-author-input" label to this issue, which indicates that we have an open question/action for you before we can take further action. This PRwill be closed automatically in 14 days if we do not hear back from you by then - please feel free to re-open it if you come back to this PR after that time. |
1 similar comment
|
Hi @@bhavanesh2001. We have added the "s/pr-needs-author-input" label to this issue, which indicates that we have an open question/action for you before we can take further action. This PRwill be closed automatically in 14 days if we do not hear back from you by then - please feel free to re-open it if you come back to this PR after that time. |
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
MapItemsLayoutwhen properties such asItemSpacing,Span, etc., change.This means that any property change within
ItemsLayouttriggers a full layout remap.For example:
When changing the
Spanof aGridItemsLayout, we can simply update the platform view’sSpanwithout 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