There was only a single command for exporting variant analysis results, which would either export the selected result or a given result. From the query history, the command was always calculating the exported result, while we can just give a query ID to export. This will create two separate commands for exporting results, one for exporting the selected results (user-visible) and one for exporting a specific remote query result. This will make it easier to add support for exporting variant analysis results. I'm not sure if there will be impact from renaming the command. I expect the only impact to be that the command history might not show the command in the correct place (i.e. it disappears from recently used commands), but please check if that is the only impact.
CodeQL for Visual Studio Code
This project is an extension for Visual Studio Code that adds rich language support for CodeQL. It's used to find problems in code bases using CodeQL. It's written primarily in TypeScript.
The extension is released. You can download it from the Visual Studio Marketplace.
To see what has changed in the last few versions of the extension, see the Changelog.
Features
- Enables you to use CodeQL to query databases and discover problems in codebases.
- Shows the flow of data through the results of path queries, which is essential for triaging security results.
- Provides an easy way to run queries from the large, open source repository of CodeQL security queries.
- Adds IntelliSense to support you writing and editing your own CodeQL query and library files.
Project goals and scope
This project will track new feature development in CodeQL and, whenever appropriate, bring that functionality to the Visual Studio Code experience.
Contributing
This project welcomes contributions. See CONTRIBUTING.md for details on how to build, install, and contribute.
License
The CodeQL extension for Visual Studio Code is licensed under the MIT License. The version of CodeQL used by the CodeQL extension is subject to the CodeQL Research Terms & Conditions.
When using the GitHub logos, be sure to follow the GitHub logo guidelines.