CalvinBackup/mvt
1
0
Fork 0
mirror of https://github.com/mvt-project/mvt.git synced 2026-09-03 08:30:51 +02:00
Code Issues Packages Projects Releases Wiki Activity

Point the README and the command docs at plugin packages

Browse Source 
Loading a command by path is for local development; a package is how a
command is distributed. The README's summary of what extends MVT now
names plugin packages and nothing else, and the section on loading a
command file says what it is for: keeping a command being written
loadable without reinstalling its package after every change.
This commit is contained in:
Donncha Ó Cearbhaill
2026-08-26 12:43:24 +02:00
parent 36d1b27c4c
commit c4215ec163
2 changed files with 12 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/development/custom_commands.md
+6 -3
View File
@@ -85,10 +85,13 @@ plugin it belongs to, so name it after the plugin, and make it a Click group
when the plugin has several operations to offer, such as
`mvt my-plugin configure`.
## Load a Command File
## Developing a Command Locally
For local commands that are not packaged, create a Python file that exports one
Click command or group named `cli`:
A package is how a command is distributed. While a command is being written,
MVT can load it straight from its file instead, so the package need not be
reinstalled after every change; an editable install of the package does the
same through its entry points. Create a Python file that exports one Click
command or group named `cli`:
```python
import click