-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Nexus sync client handler #2403
Remove Nexus sync client handler #2403
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No blocking comments for this PR but we should do another round on the API to see if we can get more consistency across the languages.
@@ -52,9 +36,8 @@ public static <T, R> OperationHandler<T, R> sync( | |||
public static <T, R> OperationHandler<T, R> fromWorkflowMethod( | |||
WorkflowMethodFactory<T, R> startMethod) { | |||
return new RunWorkflowOperation<>( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't have to be in this PR but I would to call this WorkflowRunOperation
across all SDKs.
* Get a {@link WorkflowClient} that can be used to start interact with the Temporal service from | ||
* a Nexus handler. | ||
*/ | ||
WorkflowClient getWorkflowClient(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add a method to get the nexus context too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a use case comes up yes, at least internally.
56d6c85
to
2099173
Compare
Remove Nexus sync client handler, users can now get the client with
Nexus.getOperationContext().getWorkflowClient()