Store custom field default values as JSON #5400
Labels
beta
Concerns a bug/feature in a beta release
status: accepted
This issue has been accepted for implementation
type: housekeeping
Changes to the application which do not directly impact the end user
Environment
Proposed Functionality
The CustomField model's
default
field should be a JSONField rather than a CharField.Use Case
Using a JSONField permits the storage of a default value in its native type, and avoids the need for clunky deserialization (e.g. storing the string "false" for a boolean field).
Database Changes
Migrate the
default
field to a JSONField and update all existing values accordingly.External Dependencies
None
The text was updated successfully, but these errors were encountered: