-
-
Notifications
You must be signed in to change notification settings - Fork 33.1k
Fixed #32807 -- Fixed JSONField crash when redisplaying None values. #14558
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
Conversation
Hello @strokirk! Thank you for your contribution 💪 As it's your first contribution be sure to check out the patch review checklist. If you're fixing a ticket from Trac make sure to set the "Has patch" flag and include a link to this PR in the ticket! If you have any design or process questions then you can ask in the Django forum. Welcome aboard ⛵️! |
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.
@strokirk Thanks 👍
Thanks to Alex Hill for the initial patch.
@strokirk Thanks 👍 Welcome aboard ⛵ |
Thanks! 🎉 |
See: https://code.djangoproject.com/ticket/32807
This change prevents an exception from being raised during form rendering when a JSONField is missing from form data, bringing the behaviour of JSONField in line with other fields in this case. Specifically, a blank field is rendered, accompanied by a validation error if the field is required.
Thanks to @AlexHill for the initial patch.
This takes over where #13844 left off.
Ping @felixxm for review.