spl:create
Start a new SPL model in its own workspace directory.
Usage
splent spl:create <name>
Requires detached mode. The model belongs to the workspace, not to a product.
Description
Scaffolds the model at splent_spl_<name>/, at the workspace root next to
the splent_feature_<name>/ directories, because it is authored the same
way they are. It is yours, it can be its own git repository, and it is the
source of truth until you publish it.
The _spl suffix is dropped from the directory name, since
splent_spl_cms_spl reads like a stutter. The SPL cms_spl is edited in
splent_spl_cms/. A repository cloned under the un-stripped name is still
found, so nothing is orphaned.
A brand new model has no DOI, and everything keeps working without
one. spl:publish fills it in the first time you push
the model out.
What it creates
| File | Contents |
|---|---|
metadata.toml |
[spl] name and description, and an [spl.uvl] block with the mirror and empty DOI fields |
<name>.uvl |
A minimal valid model, the root feature and nothing else. No empty mandatory or optional group, which UVL rejects. Tabs, consistent with spl:add-feature |
.gitignore |
Ignores *.uvl.bak only |
Unlike the old catalog, the model itself is tracked here. Only the
backups spl:add-feature leaves behind are noise.
See also
spl:add-feature. Grow the modelspl:publish. Push it out and get a DOI