Skip to content

docs: make the README command options match the commands - #289

Open
tylrcc wants to merge 1 commit into
NanoForge-dev:mainfrom
tylrcc:fix/issue-280
Open

tylrcc wants to merge 1 commit into
NanoForge-dev:mainfrom
tylrcc:fix/issue-280

Conversation

@tylrcc

@tylrcc tylrcc commented Nov 11, 2026 •

Copy link
Copy Markdown

Closes #280.

What changed

README-only fix. Each per-command option list now matches what the command declares in src/command/commands/*.command.ts (checked at e95b881, the commit the issue audited):

  • build, create, start: removed -c, --config — none of these commands declares it (only dev does).
  • create: removed -s, --server (no longer exists); added -t, --template; brought the -n and -p descriptions up to the declared text (plugin name form, folder defaults).
  • editor: added the missing -p, --port (default 5173).
  • dev: added the missing -e, --editor, found by the same comparison.
  • Config schema link: was https://nanoforge-dev.github.io/docs/cli/config-schema.json; the file is config.schema.json and its $id is https://docs.nanoforge.eu/docs/cli/config.schema.json (see docs/config.schema.json). The link now points there.

I corrected the lists in place rather than replacing them with links to docs/docs/commands/, so the README stays self-contained; happy to switch to the link approach if you prefer it.

Verification

I extracted every .option(...) declaration from src/command/commands/*.command.ts (including the multi-line ones in create) and compared the flag set of each README section against it programmatically: all 11 commands now match exactly, with no README-only or source-only flags. No code changed, so no tests were run.

The per-command option lists in the README did not match the
commands on main:

- build, create and start listed -c, --config, which none of
  them declares (only dev declares it).
- create listed -s, --server, which no longer exists, and
  missed -t, --template; its -n and -p descriptions also
  predated the plugin form.
- editor missed -p, --port, and dev missed -e, --editor.
- The config schema link pointed at config-schema.json on
  nanoforge-dev.github.io; the file is config.schema.json and
  its $id is on docs.nanoforge.eu.

Checked against src/command/commands/*.command.ts: every
command's README option set now equals its declared set.

Closes NanoForge-dev#280
@tylrcc
tylrcc requested a review from Exeloo as a code owner November 11, 2026 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

README command options do not match the commands

1 participant