Azure / Azure/azure-functions-durable-js
Optimize / Simplify how the IsPlayed flag is updated for CompoundTasks
- Dominant language
- TypeScript
- Stars
- 142
- Forks
- 66
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 4
Description
Follow up to: https://github.com/Azure/azure-functions-durable-js/pull/405/files#r1081924966
Our CompoundTasks have their result and `isPlayed` flag potentially set whenever their sub-tasks/children complete. When setting the `isPlayed` flag for these tasks, we're iterating over the entire set of sub-tasks, which in the extreme case may be too expensive. We should consider optimizing this logic to leverage the iterative execution style of DF.
Contributor guide
Research direction
Start with the discussion at pull request 405, especially the referenced review comment, then trace how CompoundTasks update their result and isPlayed flag when child tasks complete. Done means preserving those behaviors without iterating over the entire set of sub-tasks in the update path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100