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.

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

Add info about limitation/differences between 'shadow property' vs 'shadow navigation' #1460

Open
IdeaHunter opened this issue May 9, 2019 · 0 comments

Comments

@IdeaHunter
Copy link

There is one thing needed to be highlighted in documentation is limitation/misconception of shadow properties:
Right now if you read documentation it may give you impression that any kind of property that doesn't exists on clr type can be a shadow property, but this isn't true - shadow property can't be(or at least its not yet supported, see dotnet/efcore#3864 and aspnet/EntityFrameworkCore#15655) a property that points out to a different model aka navigation property.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants