UX: ability to influence the order of queries execution order in a query suite/pack
- Lenguaje dominante
- CodeQL
- Estrellas
- 10.1k
- Forks
- 2.1k
- Merge medio
- 2 d 15 h
- PR fusionados (30 d)
- 141
Descripción
It would be awesome if CodeQL allowed for influencing the order in which queries are run/evaluated in a [query suite](https://docs.github.com/en/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-codeql-query-suites#about-creating-codeql-query-suites) definition.
This would enhance the user experience of CodeQL in cases where a big query suite is run over a large project. By having a possibility to tell that certain queries should evaluate at the end, it would allow the users to stop the `codeql database analyze` and gather partial results from the already evaluated (and likely fast) queries and then re-run the analyzer to just work over the last possible queries.
Please see also: #17930 and #17928.
Guía de contribución
Línea de trabajo
Start by reviewing how query suite definitions are interpreted and how `codeql database analyze` executes them. The issue asks for user-controlled query ordering so that selected queries can run later and partial results can be collected; done would mean that ordering is supported in query suite definitions and works during analysis.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- security
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 30/100