lune/cmd/task/ at main · secluded.site/lune · Tangled

secluded.site / lune

0

A delightful CLI for Lunatask.app

0

lune / cmd / task /

at main 6 files

Amolith feat: add workflow-aware status validation 6mo ago

feat: add workflow-aware status validation When creating or updating tasks, status is now validated against the area's workflow. Error messages include valid options for that workflow: invalid status for workflow: 'foo' for Kanban; valid: later, next, ... MCP tools (create/update) validate when area context is available. The query tool's hardcoded status list is replaced with a dynamic one. CLI (task add/update) passes resolved area to status validation. When no area is specified, falls back to listing all valid statuses. Assisted-by: Claude Opus 4.5 via Crush

6 months ago

feat(ui): add spinner feedback for network calls Wrap all API calls with huh/spinner for immediate visual feedback. - Add generic Spin[T] and SpinVoid helpers in internal/ui/spinner.go - Update all commands making network calls to use the helpers - Use proper ellipsis (…) in spinner titles Assisted-by: Claude Sonnet 4 via Crush

7 months ago

refactor(completion): use go-lunatask All*() funcs Add TaskStatuses, Priorities, and Motivations completion functions using go-lunatask's All*() functions. Update Relationships to use AllRelationshipStrengths(). Replace completion.Static() calls and hardcoded 'started' strings with 'in-progress' to match go-lunatask's normalized enum values. Assisted-by: Claude Opus 4.5 via Crush <crush@charm.land>

7 months ago

feat(ui): add spinner feedback for network calls Wrap all API calls with huh/spinner for immediate visual feedback. - Add generic Spin[T] and SpinVoid helpers in internal/ui/spinner.go - Update all commands making network calls to use the helpers - Use proper ellipsis (…) in spinner titles Assisted-by: Claude Sonnet 4 via Crush

7 months ago

refactor(task): rename get to show for consistency Assisted-by: Claude Sonnet 4 via Crush

7 months ago

feat: add workflow-aware status validation When creating or updating tasks, status is now validated against the area's workflow. Error messages include valid options for that workflow: invalid status for workflow: 'foo' for Kanban; valid: later, next, ... MCP tools (create/update) validate when area context is available. The query tool's hardcoded status list is replaced with a dynamic one. CLI (task add/update) passes resolved area to status validation. When no area is specified, falls back to listing all valid statuses. Assisted-by: Claude Opus 4.5 via Crush

6 months ago