Apostrophe 4.4.3: improvements to "convert" allowing values that support it to remain empty #4592
boutell
announced in
Release Notes
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The following changes were made in version 4.4.3:
Fixes
field.def
when callingconvert
. Applying defaults to new documents is the job ofnewInstance()
and similar code. If you wish a field to be mandatory userequired: true
.POST
for pieces and pages with_newInstance: true
keeps any additionalreq.body
properties in the API response. This feature unofficially existed before, it is now fully supported."What is the effect of this change?" Until this change, field types like
color
that support being left blank were forced to have theirdef
value again each time the editor was opened again. This was particularly frustrating for color fields in the palette. Now they can be intentionally cleared without being reset to their initial default (def
), as long as they are not markedrequired: true
."Why was this change released early?" Normally we make new releases on a monthly cadence, however this fix was delayed past our normal monthly window for additional testing. We have decided to release it without waiting for next month's window in order to accommodate the needs of a customer.
Beta Was this translation helpful? Give feedback.
All reactions