temporalio / temporalio/temporal
[request] API needs for Temporal Web
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
logging our future internal needs on github issue as discussed with @wxing1292 and @feedmeapples
Is your feature request related to a problem? Please describe.
there are a range of small things we want, which may involve the same underlying code:
- (small) ability to query OPEN + CLOSED workflows in a single call instead of currently double call
- (nice to have) backwards pagination of a query i/o just forward pagination
- API-side FILTER of event types in History (currently doing clientside)
- Given a parent workflow, find all the child workflows
- (We want to make it easy to find the child workflows of a parent workflow in Temporal Web.)
- having both pending and complete workflows would be best, but we can settle for just pending first.
- Wenquan says implementation may be doable in mutableState if we only hold ID's of children
- more info: https://www.notion.so/PRD-for-Parent-Child-workflows-on-Temporal-Web-69c3ed9654a9471e819c13398766b0a9
Describe the solution you'd like
we are unopnionated on solution but recognize that we may need to wait a while for the underlying code for this to be in place to offer these APIs.
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 files or tests are named. Start by separating the four requested API capabilities and reading the linked Temporal Web PRD, then locate the existing query, history, and parent-child workflow API entry points. Done requires an agreed scope, API behavior, and acceptance criteria; the issue currently leaves the solution open.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100