vscode-codeql
vscode-codeql copied to clipboard
github
An extension for Visual Studio Code that adds rich language support for CodeQL
**To Reproduce** Import a database with a zipped archive. Open some file on disk outside the source archive. Select various source files in the source archive. Do VS Code command...
**Is your feature request related to a problem? Please describe.** Currently, our query results view is an editor webview, which consigns it to one of the editor panes. Occasionally, I...
I'm not exactly sure whether this is a feature request or a bug report. Regardless, this is behaviour that is not implemented, but I would expect it to be. When...
- Issue Type: `Performance` - Extension Name: `vscode-codeql` - Extension Version: `1.3.3` - OS Version: `Windows_NT x64 10.0.19041` - VSCode version: `1.49.2` Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load [GitHub.vscode-codeql-unresponsive.cpuprofile.txt](https://github.com/github/vscode-codeql/files/5291591/GitHub.vscode-codeql-unresponsive.cpuprofile.txt)
The results view could allow sorting results by which file they came from in a hybrid tree-view/table-view, where you could collapse/expand subdirectories while exploring resutls.
The extension could provide keyword proposals where appropriate. For example, in the top level, `select`, `where`, `from`, `predicate`, etc will all be available.
Currently, in order for a user to find the location of query results files, they must hunt through the logs. The query results view or query history view should include...
The user is not properly notified when the query server runs out of memory. A popup message appears with "Internal Error" on it. There are logs in the query server...
* 90% of users 90% of the time, all they need is to define their sources and sinks and plop them into a Data Flow config. * Not everyone needs...
In addition to providing code templates for query metadata written in QLDoc blocks (see #392), we should also provide proposals inside of QLDoc comment blocks. For now, I think all...