I currently inject ActivityOptions into workflow using WorkflowImplementationOptions & create ActivityStubs within the workflow.
Looks like there no option to inject ActivityStubs into the workflow (to further reduce boilerplate code). Is it because ActivityStubs need to recreated for each WorkflowExecution, like WorkflowStubs?
The main reason not to support dependency injection in the workflow is because it can break determinism.
Looks like there no option to inject ActivityStubs into the workflow (to further reduce boilerplate code).
Can you elaborate on this? You could have a factory or utility method to create activityOptions. On the other hand, it is a good practice to have different activity options for different types of activities, e.g not all activities require the same startToCloseTimeout
Antonio