dotnet / dotnet/EntityFramework.Docs

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

Open
#1,460 0 comments 0 reactions 0 assignees View on GitHub
area-entity-mapping
Dominant language
Mermaid
Stars
1.7k
Forks
2k
Avg merge
7d 23h
Merged PRs (30d)
16

Description

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 aspnet/EntityFrameworkCore#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
* Content: [Shadow Properties - EF Core](https://docs.microsoft.com/en-us/ef/core/modeling/shadow-properties)
* Content Source: [entity-framework/core/modeling/shadow-properties.md](https://github.com/aspnet/EntityFramework.Docs/blob/master/entity-framework/core/modeling/shadow-properties.md)
* Product: **entity-framework**
* Technology: **entity-framework-core**
* GitHub Login: @rowanmiller
* Microsoft Alias: **divega**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.