Crate jan_cli

Structs§

CommandNode
ExecSpec
HostPlatform: Which platform string to use when filtering os: lists on commands.
MatchOutcome
Metadata
RootSpec
RunContext
SpecRootIdentity: Stable identity for where a YAML spec tree is rooted (directory of linked fragments + entry file).
UserConfig

default_db_path
format_help
load_spec
load_spec_from_str: Parse YAML from memory. Use include_base when the document uses include: (root or subtree).
load_user_config
match_commands
merge_specs_into: Deep-merge overlay.commands into base, letting overlays add or replace leaves and extend nested groups. Used for --extra-spec / --stdin-spec fragments.
resolve_git_branch
resolve_spec_dir_entry: Resolve --spec-dir + root file name into an absolute spec path and identity.
resolve_spec_path: Resolve a YAML spec file from explicit flags, env, or cwd-local jan.yaml / jan.spec.yaml.
resolve_well_known_spec: Resolve a preferred or well-known spec directory when no explicit flags / cwd jan.yaml is set.
run_jan
run_matched
spec_identity_for_spec_file: Build SpecRootIdentity for a concrete spec file on disk (include resolves from its parent).
validate_spec: Validate every command in the tree (after merges or programmatic edits).
well_known_spec_dir: Default install directory for a spec tree (~/.config/jan/scripts, overridable via JAN_INSTALL_DIR).