Mandatory arguments are positional; quak files with no argument lists every file #211

Closed
opened 2026-10-16 14:09:46 +02:00 by clawbot · 1 comment
Collaborator

sneak (#187 (comment)): mandatory arguments should be positional, not flags, when a command has only one or two of them: quak files <collectionid>, not a --collection flag. And quak files with no arguments returns every file.

Done when: every command with one or two mandatory arguments takes them positionally; quak files with no argument lists all files and with a collection id lists that collection's; the README and --help say so; tests cover both forms.

Model: opus-5-5

sneak (https://git.eeqj.de/sneak/quak/issues/187#issuecomment-145042): mandatory arguments should be positional, not flags, when a command has only one or two of them: `quak files <collectionid>`, not a `--collection` flag. And `quak files` with no arguments returns every file. **Done when:** every command with one or two mandatory arguments takes them positionally; `quak files` with no argument lists all files and with a collection id lists that collection's; the README and `--help` say so; tests cover both forms. Model: opus-5-5
Author
Collaborator

Plan. Starts after #210 is on next, since both change bin/quak.ts and src/cli-commands.ts.

  • files is the only command with a mandatory option; get, get-thumb, backup and backup-metadata already take theirs positionally. files becomes quak files [collectionID] [--json], and the --collection option goes.
  • With a collection ID it lists that collection's files as it does today; an ID that is not one is refused as today.
  • With no argument it lists every file in the account in enumeration order, each file once. A file in several albums is listed once; its collectionID in --json is the first album that holds it. Recorded here as the reading taken: the same ID printed once per album would look like duplicates.
  • The read goes through src/cli-read.ts, whose doc covers the fresh reads of the read commands.
  • bin/quak.ts --help text, README "CLI surface", "Getting Started" and the ID paragraph.
  • Tests: files with no argument (a file in two albums printed once, text and --json), files <id>, and a bad ID.

Model: opus-5-5

Plan. Starts after https://git.eeqj.de/sneak/quak/issues/210 is on `next`, since both change `bin/quak.ts` and `src/cli-commands.ts`. - `files` is the only command with a mandatory option; `get`, `get-thumb`, `backup` and `backup-metadata` already take theirs positionally. `files` becomes `quak files [collectionID] [--json]`, and the `--collection` option goes. - With a collection ID it lists that collection's files as it does today; an ID that is not one is refused as today. - With no argument it lists every file in the account in enumeration order, each file once. A file in several albums is listed once; its `collectionID` in `--json` is the first album that holds it. Recorded here as the reading taken: the same ID printed once per album would look like duplicates. - The read goes through `src/cli-read.ts`, whose doc covers the fresh reads of the read commands. - `bin/quak.ts` `--help` text, README "CLI surface", "Getting Started" and the ID paragraph. - Tests: `files` with no argument (a file in two albums printed once, text and `--json`), `files <id>`, and a bad ID. Model: opus-5-5
Sign in to join this conversation.