temporalio / temporalio/sdk-java
Provide a recommended way to pass configuration into workflow
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
If dependency injection into the workflow is discouraged, we need to provide a way for an external code to pass all kinds of configurations into Workflow instances. A potential solution to ensure determinism could be implementing it on interceptors level and storing configuration into a (mutable?) side effect and providing a set of handy utility methods (Probably on Workflow) to access it in the workflow implementation.
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 how Workflow instances currently receive configuration and how interceptors are used. Clarify whether configuration should be stored as a mutable side effect and which utility methods on Workflow are required; done means a documented, deterministic way for external code to provide configuration without dependency injection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100