temporalio / temporalio/features
Expose Temporal Nexus operation info to Temporal Nexus operation authors
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
Like we provide activity info to activity authors and workflow info to workflow authors, we need to provide Temporal-specific Nexus operation info to Temporal Nexus operation authors. In Python/.NET this is like the activity and workflow info and only contains namespace and task queue at this time.
Per-SDK Tickets
- Go - https://github.com/temporalio/sdk-go/issues/2053
- Java - https://github.com/temporalio/sdk-java/issues/2657
- Core - N/A
- TypeScript - TODO
- Python - Done
- .NET - Done
- Ruby - TODO - no Nexus yet
- PHP - TODO - no Nexus yet
- Temporal CLI - N/A
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
Review the completed Go, Java, Python, and .NET SDK tickets linked in the issue, then locate the corresponding Temporal Nexus operation-author info entry point in the TypeScript SDK. Expose namespace and task queue there, add or update the TypeScript behavior coverage, and verify the feature tests reflect the new operation information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100