-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Metadata: Configure backing field by attribute on skip navigation #21864
Conversation
d1139af
to
633f965
Compare
You missed |
Related test question: Doesn't this mean that we are writing a lot more code to DRY little code somewhere? |
You should modify the test to look for the methods on base interfaces as well, or just add an exception
Hopefully this refactoring allows to DRY more places |
src/EFCore/Metadata/Conventions/SkipNavigationBackingFieldAttributeConvention.cs
Show resolved
Hide resolved
We were not checking collection navigations which are initialized inline and without setter. This worked fine for most part as - One sided collection were always added by convention - When there were multiple pairs and convention failed, opposite side had reference navigation which would end up throwing - Many to Many brings a twist that there is no reference on other side so in case we fail to add many to many skip navigations by convention, we would not throw.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @smitpatel! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
No description provided.