Specify error produces by invocation when awaited task fails
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 20
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
We have been implementing some promise pipeline logic and realized that it would be a good idea for invocation spec to define what happens when awaited task fails.
I think general assumption is that errors should propagate to tasks that depend on them, however I wold expect that awaiting task would get it's own receipt. I think it would be good idea to also cover in spec what the error looks like when awaited task fails.
Contributor guide
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
No source file or test is named. Start with the linked promise pipeline discussion and the invocation specification, then define the behavior for failed awaited tasks, including error propagation, the awaiting task's receipt, and the error shape; the work is done when those cases are specified clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100