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

The good news is vscode let's you name the file(s) any way you want.  The bad news is the default name is then to us.  I think standardizing on a name would be useful, especially as it would be nice to have some sort of vscode extension, or built in mechanism, to search for a file in each package, and add / update the setting in vscode.settings as one adds/removes dependencies.  This would allow autosuggest to be effective when editing html files.  I've not yet seen any effect when editing 
tagged template html, though. VSCode documentation has been inconsistent on the suggested name, so custom-elements.json works for me.

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