UX: ability to influence the order of queries execution order in a query suite/pack
- 主要言語
- CodeQL
- スター
- 10.1k
- フォーク
- 2.1k
- 平均マージ
- 2日 15時間
- マージ済み PR(30日)
- 141
説明
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.
コントリビューションガイド
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 領域
- security
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 30/100