Skip to content

Conversation

emmericp
Copy link
Contributor

If I explicitly click on "Diagnose workspace" I would expect it to show me all the diagnostics similar to how --check in a CI would check my project.

This makes it easier for users to check their whole workspace after making changes to some library or core function that potentially affects a large number of files that are usually only checked once opened.

If I explicitly click on "Diagnose workspace" I would expect it to show
me *all* the diagnostics similar to how --check in a CI would check my
project.

This makes it easier for users to check their whole workspace after
making changes to some library or core function that potentially affects
a large number of files that are usually only checked once opened.
@sumneko sumneko merged commit 630d109 into LuaLS:master Apr 22, 2024
@sumneko
Copy link
Collaborator

sumneko commented Apr 22, 2024

Thank you!

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

Successfully merging this pull request may close these issues.

2 participants