-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
Add None value handling for JSONObject builder #2021
base: master
Are you sure you want to change the base?
Add None value handling for JSONObject builder #2021
Conversation
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.
Merging this as is could cause some slowdowns because of the double check for None
that are lying around, would be nice to incorporate that into this pr too
@@ -0,0 +1 @@ | |||
Add `None` check for every put function in `JSONObjectBuilder` |
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.
No need for this changelog fragment, this change is purely internal
Co-authored-by: beagold <[email protected]> Signed-off-by: Blaze <[email protected]>
Co-authored-by: beagold <[email protected]> Signed-off-by: Blaze <[email protected]>
Co-authored-by: beagold <[email protected]> Signed-off-by: Blaze <[email protected]>
i can do that no problem |
Summary
If whe build a json object, the value should not be added to the json if its undefined type, but if its None it should just be added as None. These None checks were performed in the rest functions etc which used the JSON Object builder until now, but it makes far more sense to put this None check into the json builder.
Checklist
nox
and all the pipelines have passed.Related issues