livery.workshop._tasks¶
livery.workshop._tasks ¶
The base's verbs: what importing the workshop's plugin entry registers first.
The plugin entry (livery.workshop._mount) imports this module, then
mounts the extensions the contract lists, each through plugin()
under its own name. Importing this module registers the base's tree
alone (the quality family, the content sync): mounting the further
extensions from inside this import would deliver their tasks under the
base's identity.
Tasks assume the working directory is the workspace root; fm is
invoked there.
Functions:
| Name | Description |
|---|---|
extensions |
Print the workspace's extensions in mount order. |
link_task_names |
Link task names to the contract's |
extensions ¶
Print the workspace's extensions in mount order.
The lists are the whole of discovery: what shapes this repository
is exactly what it prints, and the instance's own files always
win last. The extensions a package's set holds come first, each
with the packages whose sets hold it, then [workspace]
extensions.
Source code in packages/workshop/src/livery/workshop/_tasks.py
link_task_names ¶
link_task_names(inv: Invocation) -> None
Link task names to the contract's [workspace] docs-url, when it sets one.
A configured docs-url comes first, and an extension that links
task names to pages of its own leaves this key's template in place.
The contract is read raw, as the mount reads it: the hook runs on
every command, fm sync among them, so a template footman cannot
fill is named on stderr and links nothing, and the command goes on.