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

VSCode: "Pull diagnostics on save" setting is not working #2034

Closed
mckeed opened this issue May 10, 2024 · 3 comments
Closed

VSCode: "Pull diagnostics on save" setting is not working #2034

mckeed opened this issue May 10, 2024 · 3 comments
Assignees
Labels
bug Something isn't working Stale

Comments

@mckeed
Copy link

mckeed commented May 10, 2024

Description

When I set "rubyLsp.pullDiagnosticsOn": "save", diagnostics do not show up after saving a file.

Reproduction steps

  1. Open a workspace in VSCode where Ruby LSP works properly
  2. Change the rubyLsp.pullDiagnosticsOn setting to "save"
  3. Make a syntax error in an open ruby file and save the file.
  4. The error is not highlighted.
  5. Closing the tab and re-opening the file highlights the error as expected.
@mckeed mckeed added the bug Something isn't working label May 10, 2024
@andyw8
Copy link
Contributor

andyw8 commented May 10, 2024

👋 Thanks for the report, I am able to reproduce.

@andyw8
Copy link
Contributor

andyw8 commented May 10, 2024

Observations:

  • By default, when we make a change to a file, a textDocument/diagnostic is sent.
  • With rubyLsp.pullDiagnosticsOn set to save, and we use "Save Without Formatting", there is a notification for didChangeWatchedFiles, but not for textDocument/diagnostic.
  • With rubyLsp.pullDiagnosticsOn set to save, and we save normally, there are notifications for textDocument/didChange and workspace/didChangeWatchedFiles.

Copy link
Contributor

This issue is being marked as stale because there was no activity in the last 2 months

@github-actions github-actions bot added the Stale label Jul 10, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Stale
Projects
None yet
Development

No branches or pull requests

3 participants