CLI command
jeden config get
Read one effective schema-backed setting.
Exact invocation#
jeden config get <key> [--json] [--cwd path]Inputs and options#
- Required: an exact key from the setting schema, including
contracts.communication,contracts.functionality,communication.mode, or one of the fourcommunication.*overrides. Optional:--jsonfor metadata and--cwdfor the project layer.
Output and state effect#
Prints the effective string or JSON value; JSON mode also returns type, description, default, and enum metadata. It does not write configuration. Layers apply in order: legacy user config.json, canonical user config.yml, then project config.json; an absent layer contributes nothing, but a broken earlier layer is not hidden by a later override. The real CLI journey JEDEN_BIN=target/debug/jeden JEDEN_TEST_SOURCE_REVISION=<candidate-commit> node tests/config/unreadable/layers.mjs uses an isolated home and project beneath .build/config-layers, checks precedence, invalid syntax and root shape, non-text and directory read refusals, byte preservation and recovery. Before configuration checks it requires a clean checkout at the declared revision and a native --version identity ending in that commit's short SHA. Its report retains those identity observations, executable/test digests, actual commands, statuses, output and final file observations; source authorship alone is not a passing run.
Refusals and boundaries#
key-missing:reading the key `jeden config get` acts on: config get requires a key, and the command line ends before one;key-unknown:reading the key `<key>`: unknown config key: <key>; no setting of Jeden has that name, observed: every key there is;argument-unexpected: a word after the key. Each exits2;jeden errors show jeden.configprints them with their tests.- Reading the layers is
jeden.config.read, run before every command but--version,--helpanderrors; each refusal names the file and exits1, and the file is never read as empty:layer-unreadable(configuration <path> cannot be read, with what the system answered, such as a directory in its place or bytes that are not UTF-8),layer-not-parsed(configuration <path> is not valid: it does not parse as JSON|YAML, with where the reader stopped),layer-root-not-object(configuration <path> is not valid: its root must be an object of settings, observed: what the root is) andlayer-settings-invalid(configuration <path> does not hold valid settings, with the value the settings reader names). Fix the named file or move it aside. - Before the layers,
jeden.config.environmentloads the environment files:env-file-unreadable,env-line-not-declaration(the line, counted from 1, and what it holds),env-value-not-json(a double-quoted value that is no JSON string) andenv-value-quote-open(a single quote left open; the value is not shown). Each names the file and exits1. - A command line of the wrong form (an unknown command or option, a missing, unexpected or invalid argument, a missing confirmation) prints the error and the usage and exits
2; a refusal that retrying unchanged can help (a dependency down or not answering, a rate limit) exits69; any other refusal or failure exits1. A refusal a functionality declares ends withfix: …andcause: <operation>.<cause>, andjeden errors show <operation>lists every cause of that functionality.