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 Jul 31, 2023. It is now read-only.
Providing only one linter (reek, rubocop) produces correct violation messages.
Adding two linters (reek, rubocop) should list violations from both of linters.
Actual behavior
Adding single linter produces correct messages.
In multi-linter configuration only one linter works (rubocop).
I can see that reek produces violation messages, and they are displayed in VSCode UI.
A second later rubocop finishes analysis, and results are replaced with rubocop messages.
The text was updated successfully, but these errors were encountered:
Hmm, that's interesting. Code diagnostics should be run in parallel and then flattened before being sent back to the client. I will take a look here.
Do you have an example file I can use to verify? I've got a few I use for development but a specific example would be great if you are willing to share.
Your environment
vscode-ruby
version: 0.24.2Expected behavior
Providing only one linter (reek, rubocop) produces correct violation messages.
Adding two linters (
reek
,rubocop
) should list violations from both of linters.Actual behavior
Adding single linter produces correct messages.
In multi-linter configuration only one linter works (rubocop).
I can see that reek produces violation messages, and they are displayed in VSCode UI.
A second later rubocop finishes analysis, and results are replaced with rubocop messages.
The text was updated successfully, but these errors were encountered: