Skip to content
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

Disable completion without disabling auto-imports? #681

Open
ghost opened this issue Jul 12, 2024 · 6 comments
Open

Disable completion without disabling auto-imports? #681

ghost opened this issue Jul 12, 2024 · 6 comments

Comments

@ghost
Copy link

ghost commented Jul 12, 2024

No description provided.

@JohnnyMorganz
Copy link
Owner

Do you mind explaining your usecase here?

@ghost
Copy link
Author

ghost commented Jul 13, 2024

I have Roblox LSP and Luau LSP active since I like Roblox LSP's autocompletion, but I like Luau LSP's typing. With both of them it duplicates the autocompletion. Is there a way to disable it for Luau LSP?

@ghost
Copy link
Author

ghost commented Jul 13, 2024

image

@lolmanurfunny
Copy link

Is there a way to disable it for Luau LSP?

No, there's currently no way to disable completion in Luau LSP without also disabling auto-imports. This is because the setting responsible for auto-imports, luau-lsp.completion.imports.enabled, is under the luau-lsp.completion namespace rather than having it as its own independent setting like how Roblox LSP's config has it.

@JohnnyMorganz
Copy link
Owner

This is because the setting responsible for auto-imports, luau-lsp.completion.imports.enabled, is under the luau-lsp.completion namespace rather than having it as its own independent setting like how Roblox LSP's config has it.

This is not the reason. It does not make a difference where the config is located, and can be doable either way. Auto import is a type of autocomplete. Making it separable requires changes to our underlying completion operation structure.

@lolmanurfunny
Copy link

This is not the reason. It does not make a difference where the config is located, and can be doable either way.

I didn't intend to imply that it was. I was just trying to give a simple explanation, but I guess it was misleading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants