Add IItemProperties, IEditableCollectionView and associated types

[weshaggard]

@dotMorten commented on Tue Apr 24 2018

The IItemProperties and IEditableCollectionView in System.ComponentModel namespace are really great for describing data on ICollectionViewSource to handle dynamic datasources, where you don't have a pre-defined class to encapsulate a datamodel. For instance when dealing with generic data from any database table. It also avoids the need for reflection, as the IItemProperties provides the PropertyInfo you otherwise would retrieve through reflection.

These interfaces are useful for generating UI dynamically based on dynamic data models, for use with for instance DataGrids, form entries etc. By having your data collections implement these interfaces, specific platforms can use these interfaces to generate a UI for the data.

Doc references:

• IItemProperties
• IEditableCollectionView
• ItemPropertyInfo

---

@weshaggard commented on Fri Apr 27 2018

Moving this to corefx as I think it is more about adding them to .NET Core then to .NET Standard. Once they are in .NET Core we can consider them for a future version of the standard if necessary.

[dotMorten]

Moving this to corefx as I think it is more about adding them to .NET Core then to .NET Standard.

It's more problematic that they aren't in UWP and Mono than .NET Core where these things are used for generating dynamic complex UI. .This is all about describing your data models, which typically are written as .NET Standard assemblies.

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[dotnet-policy-service]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.