-
Notifications
You must be signed in to change notification settings - Fork 161
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
Filter files from results tree #644
Comments
Yeah, that definitely seems like a silly thing to show in the circumstances. I'll have a look when I get a tick - thanks! |
jshiell
added a commit
that referenced
this issue
Aug 8, 2024
Note that the child count is currently hard coded and hence incorrect at present, that will take a little more tweaking to fix
Basic fix is now in main; however, the trailing "x item(s)" text is incorrect and will need some further love (hence not closing this yet). |
jshiell
added a commit
that referenced
this issue
Aug 8, 2024
jshiell
added a commit
that referenced
this issue
Aug 8, 2024
jshiell
added a commit
that referenced
this issue
Aug 8, 2024
Will be in the next release. Thanks for the tip! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In version 5.92.0 I ran a scan on the entire project, which returned around 3000 issues. Only a handful are error level, so I make sure "Display Errors" is selected and none of the others.
This only has the effect of filtering the violation line, and not the file that violations were found in.
You can see in the image I need to find the angle bracket to actually locate the violation.
If there are no violations within the filter scope, the file should not be displayed in the tree.
I see now I can unfold the nodes, but still, why show me the file. If I click the violation it opens the file, and that's all I need to see.
Perhaps add a button to determine whether files are shown at all?
The text was updated successfully, but these errors were encountered: