CLI answers form fields as strings, so boolean fields are unanswerable there too #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
packages/cli/src/commands/inbox.jsanswers a form message by collecting stringvalues, the same way the UI did before floot/endo#3 was fixed. A field declared
M.boolean()therefore cannot be answered from the CLI: the daemon runsmustMatch(value, pattern)on submit and a string never satisfies a booleanpattern.
That makes
endo inboxunable to approve any deploy workflow, which is exactlythe fallback you would want when the web UI is the thing being deployed.
The shape logic already exists and is UI-independent:
@endo/spaces-util/form-fields.jsexportsfieldKind,initialFormValuesandcollectFormValues. The CLI needs the same coercion plus a way to type ananswer — accepting
true/false/yes/nofor a boolean field would do.Closing as not worth doing for now — the web UI can answer these forms since
floot/endo#3, and nobody is approving deploys from a terminal in practice.
If that changes, the shape logic is already UI-independent in
@endo/spaces-util/form-fields.js(fieldKind,initialFormValues,collectFormValues); the CLI would need that coercion plus a way to type aboolean answer.