Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add navigation configuration overloads for shared type entity types #23255

Open
Tracked by #22952
AndriySvyryd opened this issue Nov 10, 2020 · 1 comment
Open
Tracked by #22952

Add navigation configuration overloads for shared type entity types #23255

AndriySvyryd opened this issue Nov 10, 2020 · 1 comment
Labels
area-model-building punted-for-6.0 punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints. type-enhancement
Milestone
Backlog

Comments

@AndriySvyryd
Copy link
Member

AndriySvyryd commented Nov 10, 2020 •
edited
Loading

  • Generic API will be in the form of .HasOne<Dictionary<string, object>>("TypeName", e => e.Navigation)
  • Non-generic API will be in the form of .HasOne("TypeName", "Navigation"). These overloads already exist, the implementation just needs to be adjusted to take STETs into account.

Related: #21535
@AndriySvyryd AndriySvyryd mentioned this issue Nov 10, 2020
Closed
@ajcvickers ajcvickers added this to the 6.0.0 milestone Nov 13, 2020
@AndriySvyryd AndriySvyryd mentioned this issue Jul 16, 2021
Open
73 tasks
@ajcvickers ajcvickers modified the milestones: 6.0.0, Backlog Aug 12, 2021
@ajcvickers ajcvickers modified the milestones: Backlog, 7.0.0 Oct 25, 2021
@epicbugs
Copy link

Is this issue related to error what Add-Migration returns when declaring many-to-many relationship without explicit join type?

Add-Migration in EFCore 6.0.6 returns error

The entity type 'Dictionary<string, object>' cannot be added to the model because its CLR type has been configured as a shared type.

but I was unable to find any guidelines from official documentation.

@ajcvickers ajcvickers added consider-for-next-release punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints. and removed propose-punt labels Jul 7, 2022
@ajcvickers ajcvickers modified the milestones: 7.0.0, Backlog Jul 7, 2022
@smitpatel smitpatel removed their assignment Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-model-building punted-for-6.0 punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints. type-enhancement
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@ajcvickers @smitpatel @AndriySvyryd @epicbugs