-
Notifications
You must be signed in to change notification settings - Fork 56
Roadmap
Following the release of EFCore 2.1, EFCore-MongoDB will see its first official release!
As usual, the versioning of EFCore-MongoDB will be kept in sync with the current official underlying release of EF Core.
May – Preview 1 September - Preview 2 October - RTM
EFCore-MongoDB will also transition over to my LLC - Blueshift Software - around this time. As of this post, I am still in the process of setting up accounts with GitHub and 3rd party services (AppVeyor, Travis CI, MyGet, etc). Once the transition is complete, current links to this repo will forward to the new account on GitHub. Also, I will still be maintaining the code: it will just show up under the name of my LLC.
Complete support for owned type (complex types). This includes reference and collection ownership types (better support than the underlying EF Core 2.1 system), as well as complete IStateManager support for detecting sub-document changes and propagating those updates to the root document.
Support for reference navigations from owned entity sub-documents. Currently, there are a limitations in the underlying metadata system for EF Core 2.1 that make it difficult to support collection navigations from sub-documents. I am continuing to try to work this issue, but complete support for sub-document joins might take until 2.2 or 3.0.
EF Core 2.2 is projected to release by the end of the year with various small improvements. EFCore-MongoDB will follow shortly after with a small update from 2.1. Previews will begin in late October/early November, after the official release of 2.1.
I plan to factor out a NoSQL layer from the MongoDB provider containing relevant Linq-level query-layer support and generalized metadata conventions for NoSQL database providers. I will start expanding support for NoSQL databases through Couchbase, with an initial release to target the 2.2 RTM.