Editors
Your editor reads the same tool files as gspot. A pointer file at the root of each scope leads each editor extension
to its tool file under .gspot/configurations/, so the editor reports what gspot check reports.
Before you open the editor
Section titled “Before you open the editor”Run gspot install in each clone first. The tool files load their plugins from .gspot/node_modules and
.gspot/.venv, so the ESLint extension, for example, fails until gspot install puts the tools there.
How editors find the tool files
Section titled “How editors find the tool files”| Tool | Pointer |
|---|---|
| ESLint | eslint.config.mjs |
| Prettier | prettier.config.mjs |
| Stylelint | .stylelintrc.json |
| markdownlint | .markdownlint.jsonc |
| Ruff | ruff.toml |
| basedpyright | pyrightconfig.json |
| SwiftLint | .swiftlint.yml, also in Swift test folders |
.editorconfig carries the [format] settings to every editor that reads it. Some tools have no pointer; gspot passes
their tool file when it runs them, so give your editor the same path. Generated files
lists every file gspot writes.
Validate gspot.toml
Section titled “Validate gspot.toml”The JSON Schema describes every key of gspot.toml. Editors
apply it on their own once SchemaStore lists gspot.