temporalio / temporalio/sdk-typescript
[Feature Request] Expose internal-non-workflow-common functionality
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 917
- Forks
- 224
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 43
Description
Use case: https://temporalio.slack.com/archives/C01DKSMU94L/p1658777936734799
Solution
Either:
- Add to API ref
- Combine internal* packages into
common, using a separate folder & entry point for any non-workflow APIs- In this case, could we add
@temporalio/common/non-workflowto API ref?
- In this case, could we add
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
Start by reviewing the existing internal* packages and the API ref to determine which non-workflow functionality is intended for public use. Compare the two proposed approaches—adding entries to the API ref or exposing @temporalio/common/non-workflow—and confirm that the selected design makes the required functionality publicly accessible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100