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

@adamdbradley Do you have a pointer to how you are using `HTMLElementTagNameMap`?

@manucorporat Thanks for the quick PR. Seems stencil is already generating metadata for compilers and you just added one more JSON output? Glad to see such thing baked into frameworks.

No specific reasons. I don't know what setting to call if I combine both. And there are frameworks like [Mavo](https://mavo.io) which adds only global attributes but not tags.

> WASM

@arjunyel Yep. Each language targeting web will embed HTML (like JSX) or become embedded by HTML (like Vue). These metadata provide foundation for building Language Service to support those cases.

> self-describing web components

@PaulHMason You can see the discussion I brought up for Vue: https://github.com/vuejs/vue/issues/7186. I think we should leave this discussion to each framework. As long as they generate JSON of a specific format, VS Code can use it to enhance the HTML editing capabilities. For WC, I don't know enough on this matter to give an opinion. For Vue, it depends on what experience we to give for TS.

> types for Web Components

@pjmolina I don't know enough about WC to give opinions on this matter. Bringing types to Vue has been very difficult, though.

> not focus on customElements.define()

@caridy That's correct. However we should have one that can handle build outputs (glad @justinfagnani is willing to help here). This is useful for people shipping WC libraries.

It's impossible for VS Code to support each framework. Our approach has been offering building blocks (like [vscode-html-languageservice](https://github.com/Microsoft/vscode-html-languageservice]) and let framework Language Servers build upon on them ([lit-html](https://marketplace.visualstudio.com/items?itemName=bierner.lit-html), [Vetur](https://github.com/vuejs/vetur)). The `html-language-service` will expose APIs for loading additional tags/attributes, and I can imagine a React analyzer generate metadata for its components, feed them to `html-language-service` to enhance `lit-html`.

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