docvet 1.6: JSON Output, LSP Server, and Pre-Commit Hooks #341
Pinned
Alberto-Codes
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The biggest release since 1.0 — docvet went from a CLI tool to a platform you can integrate everywhere.
What shipped
JSON output —
docvet check --all --format jsongives you structured, machine-readable results. Pipe findings into dashboards, custom tooling, or CI scripts that need programmatic access to docstring quality data.LSP server —
docvet lspprovides real-time docstring diagnostics in your editor. Based on pygls, works with any LSP client — VS Code, Neovim, Helix, Sublime Text. Findings appear as inline warnings as you type.Pre-commit hook — add docvet to your
.pre-commit-config.yamland catch docstring issues before they hit the repo. Zero configuration needed.Claude Code plugin —
.claude/settings.local.jsonintegration with pre-built hooks for Claude Code users.Positional file arguments —
docvet check path/to/file.pyon all subcommands. No more--filesflag needed for quick single-file checks.Cross-platform CI — test matrix across Ubuntu, macOS, and Windows on Python 3.12 and 3.13.
Documentation
Try it
Docs · PyPI · Changelog
Beta Was this translation helpful? Give feedback.
All reactions