cli.seed_arguments
A jadpo seed command names no seed, one the project doesn't have, or more than one.
Area 14, Tools; not declinable; the next step is usually the agent's.
Why Jadpo refuses it
A seed writes records into a database, so jadpo seed runs the one you name and never another.
What it looks like
A project with no seeds, asked to run one:
jadpo seed demo error demo isn't a seed
- reason
- The project has no seeds: each is a file in
database/seeds/. - next
- Write one in
database/seeds/<name>.jadpo, asseed { … }(agent) - rule
- cli.
seed_ arguments - help
- https://jadpo.
dev/docs/errors/cli. seed_ arguments
(agent) at the end of the next: line means your coding agent can make the fix itself.
How to fix it
If the seed isn't written yet, write it in database/seeds/demo.jadpo, as seed { … }, then run it:
jadpo seed demoIt runs against the database on this machine.
Related
Markdown for agents: /docs/errors/cli.seed_arguments.md.Built from Jadpo main at aee2e8f.