-
Notifications
You must be signed in to change notification settings - Fork 44
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
fix: Allow primary field declarations on one-many #2796
fix: Allow primary field declarations on one-many #2796
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #2796 +/- ##
===========================================
+ Coverage 78.81% 78.84% +0.03%
===========================================
Files 315 315
Lines 23835 23836 +1
===========================================
+ Hits 18784 18793 +9
+ Misses 3674 3669 -5
+ Partials 1377 1374 -3
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 11 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
71231f1
to
0015887
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
958a33a
to
01caa85
Compare
Relevant issue(s)
Resolves #961
Description
Allows primary field declarations on one side of one-many.
Declaring it as primary doesn't do anything, but there is no reason it shouldn't be permitted and it definitely shouldn't have errored the way it did.