-
-
Notifications
You must be signed in to change notification settings - Fork 754
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
Avoid checking for null on non-nullable property for projection #6706
base: main
Are you sure you want to change the base?
Conversation
@PascalSenn Is this feasible? |
We did remove it once for ef core and then added it again: So i am not sure what to do now. I believe if you do not do the nullcheck then it will include all the fields from the child or something like this. |
You removed it completely, or conditionally based on the nullability of the property? Should I be seeing something significant in the test snapshots, or is there no test that would highlight the previous issue? If not, then I think that we need that test to exist in order to have some more confidence here. |
This is the context: So you only apply it when the property is nullable and ef does not complain? |
By "does not complain", you mean that the tests in |
This will quite likely fix these issues as well: |
8a97a79
to
e2d2300
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6706 +/- ##
==========================================
- Coverage 73.92% 73.91% -0.02%
==========================================
Files 2853 2853
Lines 148656 148658 +2
Branches 17271 17271
==========================================
- Hits 109895 109876 -19
- Misses 33007 33032 +25
+ Partials 5754 5750 -4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Summary of the changes (Less than 80 chars)
Closes #6604.
context.InMemory
is about.