thefrontside / thefrontside/effection
Add a dedicated error subtype for halted tasks
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 856
- Forks
- 39
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 8
Description
Effection currently appears to surface a halted task as a plain Error("halted").
That makes it hard for integrations to distinguish cooperative halt/cancellation from an actual task failure. Right now the only reliable check is string-matching on "halted", which is brittle.
It would be useful to expose a dedicated subtype for halted tasks, for example HaltedError or CancelledError, so callers can handle task halt as a first-class outcome.
Related: #977, #662.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the task halt and error-handling entry points, then review related issues #977 and #662 for the intended cancellation semantics and error name. Define the dedicated halted-task error so integrations can distinguish it from ordinary task failures, and verify that halted tasks consistently expose that subtype rather than a plain Error("halted").
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100