You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
When working in a rust file in a crate inside a larger workspace the linter continues to work, but the UI (red dots signifying issues on particular lines, etc) does not.
When I move a crate out of the workspace the UI is restored.
The text was updated successfully, but these errors were encountered:
Could you provide an example? If the document is switching scopes (languages) in the middle of the document it's possible this provider isn't getting triggered.
I'm also experiencing this. I had one crate I was working on and then moved it to a workspace because I wanted to add a proc_macro crate to the project. After moving to a workspace, I don't see any indication of the linter in the editor, but there's still an error count in the bottom left.
When I took that same crate (now a sub-directory of the workspace) and copied it to it's own directory, the linter starting working in the editor again.
Really hopes this gets fixed and thanks for your work on this package! :)
When working in a rust file in a crate inside a larger workspace the linter continues to work, but the UI (red dots signifying issues on particular lines, etc) does not.
When I move a crate out of the workspace the UI is restored.
The text was updated successfully, but these errors were encountered: