Open maximyurevich opened 1 year ago
Provide an issue description. This is not actionable
Provide an issue description. This is not actionable
[redacted]
DRY is questionable for coding but it doesn't make any sense for a config file. Specifying roots folders per language seems perfectly fine to me.
However, I do agree that adding a roots
folder to the language server config makes sense for a different reason:
Multiple different language servers may actually expect different roots for the same language.
These roots should be merged with the per-language roots.
am currently working this.
would each language-server config have several roots or a single root.
for example:
[language-server.unocss]
command = "unocss-language-server"
args = ["--stdio"]
roots = ["unocss.config.js"]
or
[language-server.unocss]
command = "unocss-language-server"
args = ["--stdio"]
root = "unocss.config.js"
am currently working this.
would each language-server config have several roots or a single root.
for example:
[language-server.unocss] command = "unocss-language-server" args = ["--stdio"] roots = ["unocss.config.js"]
or
[language-server.unocss] command = "unocss-language-server" args = ["--stdio"] root = "unocss.config.js"
several roots
Hello! Is this feature currently being worked on? If not, I would be happy to work on it.
Hello, I want use
[language-server.mylsp-name]
directive withroots = []
like in[[language]]
directive.What exists at the moment does not satisfy DRY principle
For example: