Support declarative ApiVersion over OData entity to build versioned odata model

In OData Model Configurations, it mentioned the programing way to build versioned odata model with Ignore method, that’s working but not so developer friendly.

The ask here is to support declarative way to annotate OData entity with the ApiVersion attribute, something like this without the need to manually specify PersonModelConfiguration.

public class Person
{
    public int Id { get; set; }
    public string FirstName { get; set; }
    public string LastName { get; set; }

    [ApiVersion("2.0")]
    public string Email { get; set; }

    [ApiVersion("3.0")]
    public string Phone { get; set; }
}

Or, provide an out-of-box implementation for VesionedEntityModelConfiguration.

[commonsensesoftware]

Sounds reasonable to me. I’m sure the community would appreciate that.

[chuanboz]

We had an internal discussion for this, we still want such declarative experience as that’s what our develop used to, so want to check if you accept contribution for this and I might have some time next month to submit a general implementation of VesionedEntityModelConfiguration and make it a public supported experience than our home grown private copy.