-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Complex type collection support #31237
Labels
area-complex-types
area-model-building
consider-for-next-release
punted-for-9.0
Originally planned for the EF Core 9.0 (EF9) release, but moved out due to resource constraints.
type-enhancement
Milestone
Comments
34 tasks
Note also #11799 which is about supporting tuples as well. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Note: consider #33913 when working on complex type collections. |
AndriySvyryd
added
punted-for-9.0
Originally planned for the EF Core 9.0 (EF9) release, but moved out due to resource constraints.
consider-for-next-release
and removed
consider-for-current-release
labels
Sep 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-complex-types
area-model-building
consider-for-next-release
punted-for-9.0
Originally planned for the EF Core 9.0 (EF9) release, but moved out due to resource constraints.
type-enhancement
The collections need to be ordered, since they will be mapped to JSON arrays. (Unless we allow to map to objects, see #28861)
This only covers collections of reference types. For value types see #31411
The text was updated successfully, but these errors were encountered: