CircleCI Ideas logo
CircleCI Ideas
Home
Feedback
VS Code Extension
12

    Boards

  • Feature Requests

  • Server

  • Orbs

  • Images

  • Insights & Reporting

  • Documentation

  • API

  • Runner

  • Webhooks & Notifications

  • VS Code Extension

  • CLI

  • Config

  • CD & Release Orchestration

  • Identities & Permissions

Powered by Canny

VS Code Extension

We've launched the CircleCI VS Code Extension. Feel free to give us some feedback about your experience!
posts
Only show failed tests
At the moment, the extension shows all the tests in the project. The project I'm using has over 1500 tests, so finding a test failure is hard, and I just need to open the Circle UI again. Adding a filter for failed tests or a setting to hide successful tests would be useful.
3
·

complete

Improve identification when an orb is "unused" if it's executor is used
In our pipeline, we use the CLI Orb to define an executor, and then use that executor in jobs. Interestingly, we've found v1.2 of the VS Code extension warns us that the CLI orb is unused. But if we remove it, then the warning shows up on any job where we have defined the executor as "executor: cli/default" with "Executor cli/default does not exist" (which is now correct). So we believe the error that the orb is not in use isn't quite right in this instance, if we're using the executor from the orb. (Which to be fair, does seem like an edge case!) Reproducible YAML: version: 2.1 orbs: # see warning about orb not in use cli: circleci/circleci-cli@0.1.9 jobs: do-stuff: # if orb is commented out, this line will warn the executor is unknown executor: cli/default steps: - checkout workflows: my-workflow: jobs: - do-stuff
4
·

complete

Powered by Canny