cli.dev_arguments
A jadpo dev command names an action it doesn't have, token without a user's id, or a --url the project's several stores can't share.
Area 14, Tools; not declinable; the next step is usually the agent's.
Why Jadpo refuses it
jadpo dev serves the app, and jadpo dev token <user-id> signs a token for one user from its local issuer. A token for the wrong user would test the wrong access, so it signs none until it is told whose.
What it looks like
The user's id is left out:
jadpo dev token error jadpo dev token needs a user's id
- reason
- It signs a token for that user's subject, from the local issuer
jadpo devruns in the provider's place. - next
- Run
jadpo dev token <user-id>, with the user'sid(agent) - rule
- cli.
dev_ arguments - help
- https://jadpo.
dev/docs/errors/cli. dev_ arguments
(agent) at the end of the next: line means your coding agent can make the fix itself.
A word jadpo dev doesn't take is refused too:
jadpo dev serve error jadpo dev has no serve
- reason
jadpo devserves the app;jadpo dev token <user-id>signs a token from its local issuer.- next
- Run
jadpo dev, orjadpo dev token <user-id>(agent) - rule
- cli.
dev_ arguments - help
- https://jadpo.
dev/docs/errors/cli. dev_ arguments
The answer is the same however many words follow it.
How to fix it
If you want a token, give the user's id:
jadpo dev token user_1It prints a token for that user's subject, which jadpo dev accepts.
If you want to serve the app, run it with nothing after it:
jadpo devIt serves the app and restarts it on each save.
Related
Markdown for agents: /docs/errors/cli.dev_arguments.md.Built from Jadpo main at aee2e8f.