Default values are not applied (content model)

[ollebergkvist]

Issue Summary:

When adding custom fields to the content model, default values are not being applied as expected.

Select Field (Custom Dropdown/Select Field):
When adding a custom "Select" field with a default value, the default value is not applied in the content editor or in the API response. The field remains empty until manually changed, even though a default option has been selected.

Boolean Field:
When adding a boolean field, it is not possible to set a default value via the UI. Furthermore, if the boolean field is not toggled between true/false once, it does not appear at all in the API response, rather than defaulting to false as one would expect. The absence of the boolean field in the API response is misleading and makes it difficult to know if the field was never set or if it is missing due to a bug.

Expected Behavior:

• For the "Select" field, the default value should be automatically applied in both the content editor and in the API response.
• For the "Boolean" field, if no value is explicitly set, it should default to false and be included in the API response with that value, rather than being completely absent.

Steps to Reproduce:

• Add a new custom "Select" field to a content model and set a default value.
• Add a new custom "Boolean" field and check if it allows setting a default value.
• Save the model and check both the content editor and the API response.
• Observe that the default value for the "Select" field is not applied, and the "Boolean" field is completely missing from the API response unless manually toggled.

See pictures:

[ericingram]

Thank you, we're looking into this