using-avalonia-collectionview

You can implement filtering, sorting, and grouping in Avalonia by using a dedicated collection view service that exposes an IEnumerable view, keeping ViewModels Avalonia-agnostic while supporting DataGridCollectionView or ReactiveUI-based binding.

Avalonia lacks a native unified CollectionViewSource like WPF. To achieve consistent collection views, you need a service layer that returns DataGridCollectionView or ReactiveUI DynamicData views for clean MVVM separation.

Yes, ReactiveUI with DynamicData can be used in AvaloniaUI to provide reactive, observable collections. This approach enables simple MVVM binding and clean separation for filtered and active member lists.

The best way to decouple ViewModels is using a DI-friendly service layer that processes in-memory collections and exposes an IEnumerable view, ensuring ViewModels remain Avalonia-agnostic while binding to filtered or sorted data.

Create a MemberCollectionService, register it in your DI container, and bind the generated views to your Avalonia UI. This enables deterministic filtering, sorting, and exposes AllMembers and ActiveMembers for binding.

DataGridCollectionView provides deterministic filtering and sorting returning an IEnumerable, while ReactiveUI DynamicData offers reactive observable collections. Both integrate with a DI service layer to expose views for MVVM binding.