Add Slot to render block settings in the inspector.

[mtias]

[youknowriad]

With #714 It should be easier to extract the attributes, their types and any relative information about the attribute to show in the inspector.

[mtias]

Yes, I'm trying to think what would be the best way to declare whether something appears in the regular toolbar, on the inspector, or on both.

[youknowriad]

I think the "chaining API" might be a good solution.

attributes: {
  align: metadata().isString().choices( [ 'left', 'right', 'center', 'none' ] ).description( 'Text alignment' )
  content: children().hideFromInspector()
}

We could automatically generate the form based on this

[mtias]

Perhaps, but maybe the opposite is better: showOnInspector and defaulting to hide? We also need to figure out the simplest way to provide controls for these (inputs, toggles, segmented controls, etc).

[jasmussen]

Yes, I'm trying to think what would be the best way to declare whether something appears in the regular toolbar, on the inspector, or on both.

What if we always show a copy of the Quick Toolbar at the top of the inspector, like @folletto proposed, and then show advanced settings below that. There should be room. Would that make life simpler?

[aduth]

Would a chainable API provide much benefit over a function which returns either an element or an array of field descriptions? I worry whether it'd be flexible enough, and if it's truly any more developer-friendly.

[youknowriad]

Let's move the discussion about the API here #714 (comment)

[mtias]

Going to merge this as a placeholder for the functionality as we figure out how to present it.