Re: [w3c/webcomponents] Editor support for WebComponents (#776)

> There are also "alternatives" - for example, @castastrophe let me know that they are using a JSON schema to document their web components. Here is an example https://github.com/patternfly/patternfly-elements/blob/master/elements/pfe-band/src/pfe-band.json

@daKmoR Thanks for the mention! So we are actually walking away from our schemas at the moment.  We're implementing a built-in property management system in our base class and as such, the JS of the custom element is now the source of truth for the attributes, slots, and metadata. Going forward, you'll be able to query: `PfeFoo.properties`, `PfeFoo.slots`, `PfeFoo.meta`, for information about the component. This was a critical update for us as it allowed our base class to manage prefixing, observer, and cascading.  cc @mwcz @kylebuch8

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/776#issuecomment-713604948