Repository navigation
Docs: include paths are leaf-only; record ThenInclude and Exclude decisions - #128
Merged
Merged
Conversation
…isions - Selecting fields: new section explaining that only the end of an Include path gets its scalar fields, why, the default-values gotcha, and how to write an EF Core ThenInclude chain as nested Select. - Getting started: correct "Scalar fields are always fetched". - docs/design/include-paths.md: the rationale, the rejected ThenInclude prototype, and Exclude deferred until a real case (generator setting first).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs only, no code changes.
0,Guid.Empty) and recommends projecting when that matters, and shows EF Core users how to write aThenIncludechain as nestedSelect.docs/design/include-paths.md: the design rationale. It covers why include paths are leaf-only, why EF Core-styleThenIncludewas prototyped and rejected, and whyExcludeis deferred until a real case shows up (a generator setting comes first).