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

> I would consider it a subset of what is currently in vscode.

@daKmoR I'd say it's a superset. Think of it this way:
- `slots`, `events` etc are specific to your WC. You compile them together into HTML, and browser render it.
- Similarly, you compile `description`, `slots`, `events` into a Markdown and give that to VS Code as the `description` field, which renders that in its hover and auto-completion widgets.
- I think keep the bridge just the Markdown formatted `description` is good. There's a 1-1 relationship between what data you feed VS Code & what you see on UI. Saying "now VS Code's custom data format would include `slots`, `events`, `cssProperties` and dictate how they should be rendered" limits your freedom to organize the message in the auto-completion widget, and these don't apply to scenarios outside WC.

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