-
Notifications
You must be signed in to change notification settings - Fork 0
caseworkctl init --template should publish its possible values #1025
Copy link
Copy link
Open
Labels
agent-readyReady for an implementation agent.Ready for an implementation agent.area:caseworkRegistry Casework runtime, tooling, and clientsRegistry Casework runtime, tooling, and clientscriticality:p3Priority/criticality P3.Priority/criticality P3.enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomerstriage:needs-implementationNeeds implementation.Needs implementation.
Description
Activity
Metadata
Metadata
Assignees
Labels
agent-readyReady for an implementation agent.Ready for an implementation agent.area:caseworkRegistry Casework runtime, tooling, and clientsRegistry Casework runtime, tooling, and clientscriticality:p3Priority/criticality P3.Priority/criticality P3.enhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomerstriage:needs-implementationNeeds implementation.Needs implementation.
Problem
caseworkctl init --templateaccepts a free-form string and lists no possiblevalues in its generated command metadata. Invalid values are rejected only after
argument parsing. This differs from the closed template catalog now published by
bregctl init --template.Expected
generated CLI reference.
duplicated list.
Found while reviewing #1016. The behavior predates that pull request.