docs: add glossary entry for 'spec'
This commit is contained in:
parent
062da0685c
commit
87790bbb1a
|
@ -227,6 +227,21 @@ Glossary
|
||||||
:term:`config settings<config setting>`. See also
|
:term:`config settings<config setting>`. See also
|
||||||
:doc:`narr/config/table`.
|
:doc:`narr/config/table`.
|
||||||
|
|
||||||
|
spec
|
||||||
|
As the term is used in Wutta Project context, this refers to a
|
||||||
|
string designating the import path to a particular object (class,
|
||||||
|
function etc.).
|
||||||
|
|
||||||
|
Also the term implies a certain format, namely a dotted module
|
||||||
|
path followed by colon (``:``), then object name.
|
||||||
|
|
||||||
|
For instance, ``wuttjamaican.app:AppHandler`` is the spec string
|
||||||
|
for the :class:`wuttjamaican.app.AppHandler` class (and note, the
|
||||||
|
hyperlink does not use colon, but our "spec" always does).
|
||||||
|
|
||||||
|
See also :meth:`~wuttjamaican.app.AppHandler.load_object()` (on
|
||||||
|
the :term:`app handler`) which can return any object from spec.
|
||||||
|
|
||||||
subcommand
|
subcommand
|
||||||
A top-level :term:`command` may expose one or more subcommands,
|
A top-level :term:`command` may expose one or more subcommands,
|
||||||
for the overall command line interface. Subcommands are usually
|
for the overall command line interface. Subcommands are usually
|
||||||
|
|
Loading…
Reference in a new issue