For now is nighmare, especially sharing between servers
- There are HTML, CSS, JS/TS preferences. Each one implemented manuly
- HTML server read CSS preferences but completely ignore these from JS/TS
- Vue could use HTML, LESS, JS, TS, SASS, CSS and others but each time have to implement manually
- Same problems appear in case when we introduce some global preferences (format on save, insert mode, word matching settings)
- There is no support for aliasing, for example typescript server embeded in HTML LS require different names
I think this can and should be simplified by:
- Ability to use some informations directly from vscode package.json + some standard UI editors
- Extensions that allow to register configuration sections adapters + default settings store (like settings.json in vscode)
- Maybe in future support for settings scope (workspace and project level)
I don't know where this code should be store. I did some PoC during Vue implementation and can clean this for wildwebdeveloper.common, and/or should be prepared for LSP4E directly
For now is nighmare, especially sharing between servers
I think this can and should be simplified by:
I don't know where this code should be store. I did some PoC during Vue implementation and can clean this for wildwebdeveloper.common, and/or should be prepared for LSP4E directly