-
Notifications
You must be signed in to change notification settings - Fork 185
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
Improve UI feedback when there are 0 alerts
#236
Labels
enhancement
New feature or request
Comments
aeisenberg
added a commit
to aeisenberg/vscode-codeql
that referenced
this issue
Mar 18, 2020
Right clicking on the history page will now have a new option to show the associated log. Closes github#236 Closes github#234
aeisenberg
added a commit
to aeisenberg/vscode-codeql
that referenced
this issue
Mar 18, 2020
Right clicking on the history page will now have a new option to show the associated log. Closes github#236 Closes github#234
aeisenberg
added a commit
to aeisenberg/vscode-codeql
that referenced
this issue
Mar 18, 2020
When removing query history item from view, also remove the side log. Log files can be large, so ensure they don't stick around. Last piece of github#236 and github#234.
aeisenberg
added a commit
to aeisenberg/vscode-codeql
that referenced
this issue
Mar 19, 2020
When removing query history item from view, also remove the side log. Log files can be large, so ensure they don't stick around. Last piece of github#236 and github#234.
This was referenced Sep 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
While developing and running a query, it is possible to have 0 results in the formatted
alerts
table, but a non-zero number of tuples in the#select
table. This can happen if the selected entity is missing location information, or if there is a mismatch between the query metadata and the columns in theselect
clause. This commonly trips up both new and experienced writers and leads to time wasted debugging the query's logic.Describe the solution you'd like
Describe alternatives you've considered
Alternatively, make 0 alerts a special case, and in this case have an annotation pointing the user to the
#select
table or the table dropdown.Additional context
The text was updated successfully, but these errors were encountered: