-
Notifications
You must be signed in to change notification settings - Fork 72
fix: Default json value #4064
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: Default json value #4064
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #4064 +/- ##
===========================================
+ Coverage 73.97% 74.04% +0.07%
===========================================
Files 477 477
Lines 43754 43766 +12
===========================================
+ Hits 32367 32406 +39
+ Misses 9176 9158 -18
+ Partials 2211 2202 -9
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 9 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
ChrisBQu
left a comment
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.
| // Since setting a default value to nil is the same as not providing one, | ||
| // it is safer to return an error to let the user know something is wrong. | ||
| if value == nil { | ||
| // Exception: JSON fields can have nil as a valid default value |
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.
question: Why do we treat the JSON type differently?
Relevant issue(s)
Resolves #3146
Description
Fix default json value by properly converting it's value into a corresponding type.