- Issue created by @wim leers
- 🇺🇸United States effulgentsia
Even though my quote referenced in the issue summary was in the issue about the "page data" form, it was actually a statement about the component inputs form and just used as a point of comparison. So, re-titling this issue accordingly.
Currently, there is no client-side transformation that runs when widget inputs are updated on the page data form, so this issue isn't applicable there, though it's possible that at some point we'll want to open a separate issue to add client-side transformations on the page data form. I don't think there's currently a use-case for that though, since the fields on the page data form are intentionally the ones that (for the most part) don't have any representation in or impact on the preview (with the exception of potentially changing the content of Blocks, such as the page title block).
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
I don't think there's currently a use-case for that though, since the fields on the page data form are intentionally the ones that (for the most part) don't have any representation in or impact on the preview (with the exception of potentially changing the content rendered in Blocks, such as the page title block).
That will completely change with 🌱 [META] 7. Content type templates — aka "default layouts" — clarify the tree+props data model Active !
