feat: expand object + DZ fields via settings parameter >open<

[ma-schmidt-de]

Changes

The new attribute open of interface CmsModelFieldSettings controls whether the accordion renderer of objects and dynamic zones are expanded by default.
BREAKING CHANGE: none
Closes #4109

How Has This Been Tested?

Manually.

Documentation

I'm planning to add a "How to" section below this on in webiny.com/docs:
https://www.webiny.com/docs/headless-cms/extending/content-models-via-code#how-to-set-a-default-value-of-a-field

[Pavel910]

That's a nice PR @ma-schmidt-de, but let's make it even better. The next branch now has this new feature called "renderer settings". Check out the draft changelog: https://docs-webiny-com-git-release-5400-webiny.vercel.app/docs/release-notes/5.40.0/changelog#field-renderer-settings

This feature that you've implemented would make much more sense as a renderer settings, not a field setting in general. If you think about it, what does open mean on a boolean field? So let's move this flag to renderer settings for dynamicZone and object field renderers. That way each renderer can have its own very specific settings, and the general field definition is not cluttered with unrelated properties.

Here's a reference to how you would use these settings in a renderer: https://github.com/webiny/webiny-js/blob/next/packages/app-headless-cms/src/admin/plugins/fieldRenderers/ref/advanced/components/ReferencesDialog.tsx#L81

And here's how you define new renderer settings, on a renderer level:
https://github.com/webiny/webiny-js/blob/next/packages/app-headless-cms/src/admin/plugins/fieldRenderers/ref/advanced/detailedReferencesRenderer.tsx#L40-L42

The settings will be stored into the renderer: { name: "...", settings: { ... } }.

[ma-schmidt-de]

Sounds great, @Pavel910
I'll look into this and refactor my PR accordingly. 👍

[ma-schmidt-de]

Let me actually open a new PR. I got mixed up a bit with branches in my fork. 🙂

[ma-schmidt-de]

new PR: #4155