-
Notifications
You must be signed in to change notification settings - Fork 56
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: Treat explicitly set nil values like omitted values #3101
fix: Treat explicitly set nil values like omitted values #3101
Conversation
Note: This is not desirable :)
These are two different bugs, but they are similar and small, so I am being lazy and sorting them out at the same time.
Field values should not behave differently depending on whether they were ommited from the initial create call.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #3101 +/- ##
===========================================
- Coverage 79.81% 79.73% -0.08%
===========================================
Files 351 351
Lines 27335 27351 +16
===========================================
- Hits 21816 21808 -8
- Misses 3982 3998 +16
- Partials 1537 1545 +8
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.
|
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
…rk#3101) ## Relevant issue(s) Resolves sourcenetwork#3100 ## Description Treat explicitly set nil values like omitted values.
Relevant issue(s)
Resolves #3100
Description
Treat explicitly set nil values like omitted values.
There were a couple of bugs here, I suggest reviewing commit by commit as the old behaviour was documented before being corrected.