temporalio / temporalio/sdk-java
Pluggable activity name provider
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
The activity type name is automatically generated from its method name. Different users of the SDK have different opinions on how this name should be generated. For example, see this forum post.
Describe the solution you'd like
The proposal is to make activity name generation pluggable through ClientOptions and WorkerOptions. This way each user can implement its own standard to name activities automatically.
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 examining the ClientOptions and WorkerOptions entry points named in the issue, then trace where activity names are generated from method names. Define the provider configuration and verify that users can supply different naming standards through both options without changing the default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- 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