- From: Bruce B. Anderson <notifications@github.com>
- Date: Fri, 18 Oct 2019 14:53:23 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 18 October 2019 21:53:26 UTC
If we were to introduce something in package.json, looking at the schema: https://schemastore.azurewebsites.net/schemas/json/package.json, I'm wondering if it would make most sense, rather than specifying a file path, to specify a directory, e.g.:
```JSON
"directories": {
"custom-element-reference": "/my-docs-folder/"
}
```
which could allow for [different language](https://github.com/AlmirKadric-Published/jsdoc-i18n) extensions (e.g. custom-elements-en-US.json)?
@octref , are there any plans/appetite for VS Code to support something like this (eventually)?
i.e. recognize a setting in package.json to look for (language-aligning) json files, which could get added / removed as dependencies are added / removed into the .settings file (or just load into memory directly)?
Any suggestions on how best to align with what would work in VS Code?
--
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-543968714
Received on Friday, 18 October 2019 21:53:26 UTC