All tutorials

Findings in the editor

Cordon 0.6.01 sections · 1 diagramView this tutorial on GitHub

The VS Code extension shows Cordon's findings where you are already looking: on the line, with the fix beside it.

Findings in the editor, figure 1
┌──────────────────────────────────────────────────────────────────────────┐
│    install        pipx install cordon-scanner                            │
│                   then cordon-<version>.vsix from the release page       │
│                                                                          │
│    it runs        on opening a folder, on save, and on                   │
│                   'Cordon: Scan workspace'                               │
│                                                                          │
│    it never       sends anything anywhere, runs in a folder you have not │
│                   trusted, or lets a repository choose what it executes  │
└──────────────────────────────────────────────────────────────────────────┘
settingdefault
cordon.pathcordon-scannermachine setting only: a workspace cannot change it
cordon.scanOnSavetrue
cordon.minimumSeveritylowfindings below this are not shown

Findings without a line -- repository-wide ones, or members of an archive -- go to the Cordon output channel, and the status bar shows the count.

Next: 21 · Reviewing a dependency update.