Move ItemsRepeater to a dedicated repository #14989
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
You can test this PR using the following package version. |
grokys
approved these changes
Mar 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does the pull request do?
See https://github.com/AvaloniaUI/Avalonia.Controls.ItemsRepeater
In 11.0 we moved ItemsRepeater from the Avalonia package into Avalonia.Controls.ItemsRepeater package, starting migration out of this control.
Primary reason is that ItemsRepeater proved to be a very difficult control, with some major issues in upstream, as well as Avalonia specific problems.
As a result, it was decided to fix our old ItemsControl instead of continuing with ItemsRepeater, which was done for 11.0.
Instead of spending more time on fixing ItemsRepeater, we want to continue improving ItemsControl instead.
Breaking changes
No, since ItemsRepeater was already extracted into a separated nuget package for 11.0.
It will make no difference for the consuming applications.