fix: graph export's command option conflicts with global option

--output was being used as a global and command option. This resulted in
buggy, coupled behavior e.g. unable to set a global output unless the
export file was named human, edn or json. `--ouput` was also
not listed as a command option which was confusing. Renamed the command
--ouput to --file for explicit and uncoupled behavior
This commit is contained in:
Gabriel Horner
2026-03-02 12:12:51 -05:00
committed by rcmerci
parent 0331c598df
commit 859c4cee41
8 changed files with 38 additions and 33 deletions

View File

@@ -19,8 +19,8 @@ Related: Builds on docs/agent-guide/004-logseq-cli-verb-subcommands.md and docs/
Prefer graph-scoped subcommands to keep import/export with graph management:
- `logseq graph export --type edn --output <path> [--repo <graph>]`
- `logseq graph export --type sqlite --output <path> [--repo <graph>]`
- `logseq graph export --type edn --file <path> [--repo <graph>]`
- `logseq graph export --type sqlite --file <path> [--repo <graph>]`
- `logseq graph import --type edn --input <path> --repo <graph>`
- `logseq graph import --type sqlite --input <path> --repo <graph>`