Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

choose lsp implementation based upon file path #12239

Closed
mountainpath9 opened this issue Dec 12, 2024 · 0 comments
Closed

choose lsp implementation based upon file path #12239

mountainpath9 opened this issue Dec 12, 2024 · 0 comments
Labels
C-enhancement Category: Improvements

Comments

@mountainpath9
Copy link

I have a repo with the following structure

deno.json
package.json
deno/src/**/*.ts                           # needs deno lsp
ts/src/**/*.ts                             # needs nodets lsp

and want to create a .helix/languages.toml file such that the appropriate lsp is started depending on the opened typescript file.

It seems like #8696 was intended to address this, but it's not clear that it does.

The workspace is structured with both deno.json and package.json in the root so that both yarn and deno can be executed from the root.

Should the language server configuration support file globbing patterns in a way similar to the language configuration ?

@mountainpath9 mountainpath9 added the C-enhancement Category: Improvements label Dec 12, 2024
@kirawi kirawi converted this issue into discussion #12240 Dec 12, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
C-enhancement Category: Improvements
Projects
None yet
Development

No branches or pull requests

1 participant