v11-Prev 5 - After Upgrading Prism Module Region Fails Inside of ItemsControl #47
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.
Issue
After upgrading to Avalonia v11-Preview5, Prism Modules can fail to register a region defined in XAML.
The error is being thrown in
ItemsControlRegionAdapter.Adapt(IRegion region, ItemsControl regionTarget)
when it attempts to setregionTarget.Items = region.Views;
. Which is equivalent toAvalonia.Collections.AvaloniaList<object> = Prism.Regions.ViewsCollection
. To address this,IViewsCollection
may need to inheritIList
(by why all a sudden?)Reproduce
Research
Currently, I'm looking into what changed in the architecture to warrant this modification. This could be why the sample app, ViewDiscovery, is also failing to operate correctly
Error Message:
Call Stack:
References