Is WebComponent a Container for other Elements (low prio)

[jogibear9988]

We should also have a configuration to tell if a WebComponent is a container for other elements (maybe a array of querySelectors wich define possible elements)

[jogibear9988]

This is needed for a good designer experience, so I know if I could drag other components into

[thepassle]

How is this different from slots?

[jogibear9988]

Not every custom element uses slots

[thepassle]

Then im not sure what you mean. Can you provide some more information/context and some code examples, and a proposal of what you'd like to happen in the schema?

[jogibear9988]

Okay, maybe we also could use the the empty slot.
But then the empty slot is mandatory, means if it is not there the element is not allowed to have children

[jogibear9988]

or we do something like this
uses #46

   {
        name: "",
        allowedChildren: [":not(*)"]
    }

[break-stuff]

We use this plugin to create a custom related property to our manifest, but it would be really nice (especially for documentation purposes) to have this be part of the official schema. We use it to associate components like tabs, tab, and tab-panel or combobox and option.