Discuss where Inspector display/presentation metadata should live/look like about aframe-registry HOT 7 CLOSED

Do you mean adding things like tags right? In that case I believe it could be better to live here in the registry so we could modify them, and it will work both for the registry webpage or the inspector and we don't rely on the component package in case we want to rename some tags or whatever

from aframe-registry.

Like grouping and sorting of properties in the Inspector Components panel.

from aframe-registry.

Ah ok, that properties probably should stay on the component, so each one could decide how the component will be shown on the inspector, or just use the default visualization and don't define anything. Similar to how unity plugins works, you can just place there the parameters or get fancy and define a much nicer UI

from aframe-registry.

So an inspector (aframe?) package.json field?

from aframe-registry.

Per component / property inspector hints should live in the component schema.

from aframe-registry.

Yes, I don't like using package.json for that, I think it should belong to the component definition file, inside the schema or wherever.

from aframe-registry.

overloading the schema feels okay now as the Inspector becomes more and more important.

from aframe-registry.