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

Remove notification boxes #383

Closed
oliversalzburg opened this issue Jan 19, 2021 · 2 comments
Closed

Remove notification boxes #383

oliversalzburg opened this issue Jan 19, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@oliversalzburg
Copy link

Current Version

0.12.1

Use-cases

When editing modules in VS Code to which terraform-ls can not determine the root module, it will directly call into VS Code API to open GUI notifications. The LS will keep popping up the notification consistently for every single time the active document is changed.

Editing standalone modules can not be so rare of a use case that it requires this level of interference.

Attempted Solutions

The calls are hardcoded at https://github.com/hashicorp/terraform-ls/blob/main/internal/langserver/handlers/did_open.go#L138 and https://github.com/hashicorp/terraform-ls/blob/main/internal/langserver/handlers/did_open.go#L93 and can not be disabled by themselves.

Proposal

The LS should not invoke APIs that directly interfer with the UI. There is an existing output channel to communicate any issues and if user interaction is required, it should be proxied through the main IDE extension.

The IDE extension is presumeably far better equipped to handle these notifiations in a non-distracting way (like a status bar indication).

Related LSP methods

References

@radeksimko
Copy link
Member

Hi,
The issue is not addressed yet, but we have a plan for addressing it and I'm just merging all the issues with the same root cause, such as this one, into a single issue: #424

Thank you for your understanding and patience.

@ghost
Copy link

ghost commented Mar 27, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the context necessary to investigate further.

@ghost ghost locked as resolved and limited conversation to collaborators Mar 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants