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

@justinfagnani 
I agree, we could and show be able to pack more useful information, like CSS vars that apply (CSS autocompletion), the "slots" provided by a component or even the "type" of an attribute. While we all know HTML attributes might only be strings. The valid values differ:

- Any string value
- "true" | "false"
- "on" | "off"
- any union of strings `(side: 'left' | 'right')`
- if an attribute is required or not

I think the `.json` is looking good, no need to ship all this features the first day, very promising!

@PaulHMason 
>(even if that means just attaching the json description file content as a static property to the class definition)

I don't think we should make web components bigger to fix a DX issue, not a runtime one. It's a matter of tooling, polymer, stencil or even VScode itself could parse web components and "auto-generate" whatever the metadata is required.

@octref
Question, why do we need "two" .jsons?

-- 
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-443144904