mq-content-lint for VS Code

A thin Language Server Protocol client for mq-content-lint-lsp, showing mq-content-lint's diagnostics inline as you edit and offering its fixes as quick actions.

Requirements

The mq-content-lint-lsp binary — this extension is a client, it doesn't reimplement any linting itself. On macOS (Apple Silicon), Linux (x64/arm64), and Windows (x64), nothing to install: the extension downloads a matching prebuilt binary from this repo's GitHub Releases the first time it activates, verifies it against the release's checksums, and caches it in global storage. On other platforms (e.g. Intel Mac), install it yourself:

cargo install mq-content-lint --locked --features lsp

That installs both mq-content-lint (the CLI) and mq-content-lint-lsp (the language server) — lsp is opt-in, so don't drop it from the command. An existing PATH install is always preferred over downloading. Set mqContentLint.serverPath to skip both and point at a specific binary.

Features

• Diagnostics update live as you type or save (the server re-lints on every change), each carrying its rule id (e.g. image_missing_alt) so the Problems panel shows exactly which rule fired.
• Fixable diagnostics offer a quick fix (lightbulb / Cmd+.) that applies exactly what mq-content-lint --fix would.
• Hovering a diagnostic shows the rule's help text (the same "how to fix this" hint the CLI prints below each finding).
• mq-content-lint: Fix Document command (Command Palette) applies every available quick fix across the whole file in one edit, matching mq-content-lint --fix's single-pass semantics.
• mq-content-lint: Restart Server command, and the server restarts automatically whenever an mqContentLint.* setting changes.
• Config resolution (including config cascading) is handled server-side per file, the same as the CLI — there's no separate config-path setting to keep in sync. Editing an mq-content-lint.toml re-lints every open document automatically (no restart needed) whenever VS Code supports watched-file notifications, which it does out of the box.

Settings

Development

cd editors/vscode
npm install
npm run compile   # or `npm run watch`

Press F5 in VS Code (with this directory open) to launch an Extension Development Host for manual testing — make sure mq-content-lint-lsp is built and on PATH first (cargo install --path . --locked from the repo root, or point mqContentLint.serverPath at target/debug/mq-content-lint-lsp), since the auto-download only fetches from tagged GitHub Releases, not local builds.

Run npx vsce package to produce a .vsix for local installs or manual upload; there's no CI publish step yet.