fix: stop self-referential FK recursion#4
Draft
dkattan wants to merge 2 commits into
Draft
Conversation
Split direct foreign-key discovery from the shared-key fallback heuristics so self-referential and non-conventional navigation names don't recurse through ForeignKeyProperty while model validation is still trying to classify the relationship. Add regression coverage for a self-referential navigation and for a consumer that targets that entity. Validated with Coalesce tests on net10 and with Immybot's ImmybotDbContext, where generation now reaches normal model validation errors instead of stack overflowing. Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
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
1 participant
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.
Summary
Docs