Context
The commands in this section are available when the following packages are installed:
@uniformdev/cli
@uniformdev/context
Aggregates
Get aggregate
uniform context aggregate get <id>
List aggregates
uniform context aggregate list
Pull aggregate
uniform context aggregate pull <directory or file path>
- If a directory path is specified, a separate file is created for each aggregate.
- If a file path is specified, all aggregate definitions are saved in a single file.
If file name is specified, CLI will override only corresponding part of it (e.g. pulling Project Map will only override project map section, but leave Canvas section in the same file intact). It allows you to create single file containing whole project export (Canvas + Context + Project Map). Not recommended for big projects. Check for more here
Push aggregate
uniform context aggregate push <directory or file path>
- If a directory path is specified, the aggregates defined in the files in the directory used.
- If a file path is specified, the aggregates in the file are used.
Remove aggregate
uniform context aggregate remove <id>
Update aggregate
uniform context aggregate update <filename>
Enrichments
Get enrichment
uniform context enrichment get <id>
List enrichments
uniform context enrichment list
Pull enrichment
uniform context enrichment pull <directory or file path>
- If a directory path is specified, a separate file is created for each enrichment.
- If a file path is specified, all enrichment definitions are saved in a single file.
If file name is specified, CLI will override only corresponding part of it (e.g. pulling Project Map will only override project map section, but leave Canvas section in the same file intact). It allows you to create single file containing whole project export (Canvas + Context + Project Map). Not recommended for big projects. Check for more here
Push enrichment
uniform context enrichment push <directory or file path>
- If a directory path is specified, the enrichments defined in the files in the directory used.
- If a file path is specified, the enrichments in the file are used.
Remove enrichment
uniform context enrichment remove <id>
Update enrichment
uniform context enrichment update <filename>
Manifests
Get manifest
uniform context manifest get <filename>
Publish manifest
uniform context manifest publish
Quirks
Get quirk
uniform context quirk get <id>
List quirks
uniform context quirk list
Pull quirk
uniform context quirk pull <directory or file path>
- If a directory path is specified, a separate file is created for each quirk.
- If a file path is specified, all quirk definitions are saved in a single file.
If file name is specified, CLI will override only corresponding part of it (e.g. pulling Project Map will only override project map section, but leave Canvas section in the same file intact). It allows you to create single file containing whole project export (Canvas + Context + Project Map). Not recommended for big projects. Check for more here
Push quirk
uniform context quirk push <directory or file path>
- If a directory path is specified, the quirks defined in the files in the directory used.
- If a file path is specified, the quirks in the file are used.
Remove quirk
uniform context quirk remove <id>
Update quirk
uniform context quirk update <filename>
Signals
Get signal
uniform context signal get <id>
List signals
uniform context signal list
Pull signal
uniform context signal pull <directory or file path>
- If a directory path is specified, a separate file is created for each signal.
- If a file path is specified, all signal definitions are saved in a single file.
If file name is specified, CLI will override only corresponding part of it (e.g. pulling Project Map will only override project map section, but leave Canvas section in the same file intact). It allows you to create single file containing whole project export (Canvas + Context + Project Map). Not recommended for big projects. Check for more here
Push signal
uniform context signal push <directory or file path>
- If a directory path is specified, the signals defined in the files in the directory used.
- If a file path is specified, the signals in the file are used.
Remove signal
uniform context signal remove <id>
Update signal
uniform context signal update <filename>
Tests
Get test
uniform context test get <id>
List tests
uniform context test list
Pull test
uniform context test pull <directory or file path>
- If a directory path is specified, a separate file is created for each test.
- If a file path is specified, all test definitions are saved in a single file.
If file name is specified, CLI will override only corresponding part of it (e.g. pulling Project Map will only override project map section, but leave Canvas section in the same file intact). It allows you to create single file containing whole project export (Canvas + Context + Project Map). Not recommended for big projects. Check for more here
Push test
uniform context test push <directory or file path>
- If a directory path is specified, the tests defined in the files in the directory used.
- If a file path is specified, the tests in the file are used.
Remove test
uniform context test remove <id>
Update test
uniform context test update <filename>