cli.migrate_arguments
A jadpo migrate command names no action, one it doesn't have, a purpose for an action that takes none, or a --drop of what isn't retired.
Area 14, Tools; not declinable; the next step is usually the agent's.
Why Jadpo refuses it
jadpo migrate new writes the next migration, apply runs a database's pending ones, and status lists them. Changing a database is never done for a word it doesn't know.
What it looks like
The action is misspelt:
jadpo migrate aply error aply isn't something jadpo migrate does
- reason
jadpo migrate newwrites the next migration,applyruns a database's pending ones, andstatuslists them.- next
- Use
jadpo migrate new,jadpo migrate applyorjadpo migrate status(agent) - rule
- cli.
migrate_ arguments - help
- https://jadpo.
dev/docs/errors/cli. migrate_ arguments
(agent) at the end of the next: line means your coding agent can make the fix itself.
A purpose after an action that takes none is refused rather than ignored:
jadpo migrate status add_due_date error jadpo migrate status takes no purpose
- reason
- Only
jadpo migrate newtakes a purpose;add_due_datewould be ignored. - next
- Run
jadpo migrate status(agent) - rule
- cli.
migrate_ arguments - help
- https://jadpo.
dev/docs/errors/cli. migrate_ arguments
How to fix it
If you meant to apply the migrations, name apply:
jadpo migrate applyIt runs the pending migrations on the database config.database_url names.
If you meant a new migration, give the purpose to new:
jadpo migrate new add_due_dateIt writes the next migration, named after its purpose.
Related
Markdown for agents: /docs/errors/cli.migrate_arguments.md.Built from Jadpo main at aee2e8f.