You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
ID: 550a3c36-7f1d-efa7-3ed8-769720168da4
Version Independent ID: 627c4301-e00d-826e-d545-3a244305dec9
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.
The text was updated successfully, but these errors were encountered: