-
Notifications
You must be signed in to change notification settings - Fork 202
Support for query suites #615
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
Comments
It sounds like you are asking for 3 separate and related features here:
|
Has the team started implementing it yet? |
Not yet. To run query suites, I suggest using the cli directly. |
On a similar note for query suites, is there a way to run query suites on the selected variant analysis repositories? Either a way through the CLI or the directly through the extension interface? |
No. Variant analysis runs one query at a time. |
Is your feature request related to a problem? Please describe.
It'd be great to have the extension understend CodeQL query suites. This would ideally cover both authoring them and executing query suites on the currently-selected database.
Describe the solution you'd like
The
*.qls
format is effectively YAML with a particular schema, so switching to YAML mode at least gives syntax highlighting at the moment. Having the schema used automatically for auto-complete suggestions and error checking would be great, though.For bulk query execution, selecting a
*.qls
file would be more flexible than the current "run all queries in this folder" approach. There's a slight UI challenge around how to make well-known query suites discoverable.Describe alternatives you've considered
The current workaround is to edit
*.qls
files after manually selecting YAML mode, and to use the CodeQL CLI to run query suites, though that doesn't insert them into the query history view.The text was updated successfully, but these errors were encountered: