Good news: this is another thing that we felt was really important to take to the OData v4 protocol committee. This feature will be available in the near future as we finish work on our v4 stack.Mark Stafford commented
@Petr - The core libraries (ODataLib and down) will have support for containment in the next couple of months. Web API will take advantage of that support probably in 1Q 2014. I'm not sure about the schedule for WCF Data Services explicitly, though.
1,081 votes14 comments · [Closed] WCF Data Services Feature Suggestions · Flag idea as inappropriate… · Admin →
Good news: this is coming – and not just on entity types but on complex types as well. Enums are part of the OData v4 protocol. In fact, it was one of the things we argued vociferously for precisely because of the number of votes on this issue.Mark Stafford commented
@All - it's hard to understand why stuff like this takes time to implement sometimes (especially when EF implemented it comparatively quickly). A large part of the reason is simply because protocols take so long to modify. Our v4 train has been in process for nearly two years now, and it's happening comparatively quickly.
That said, it looks like we are still on track to have OData v4 standardized by OASIS later this year (no promises, we at Microsoft are only part of the process). The implementation of enums in our stacks will not come before the protocol is standardized, and will likely actually land sometime after the protocol is standardized. On the plus side, we hear you very clearly on this issue and I've advocated for it a ton at Microsoft because of the feedback both on this forum and elsewhere.
What I can say is that we do have resources working on the feature right now, and the design is clear now that the v4 protocol deals with it. That means I would expect the feature to land either later this year or in the first quarter of next year. Again, no promises but we really want to get this to you and we think you deserve it. :)