-
Notifications
You must be signed in to change notification settings - Fork 216
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
Workflow update client API refactor #1489
Workflow update client API refactor #1489
Conversation
client/client.go
Outdated
// directly from this function call. | ||
// NOTE: Experimental | ||
UpdateWorkflowWithOptions(ctx context.Context, request *UpdateWorkflowWithOptionsRequest) (WorkflowUpdateHandle, error) | ||
UpdateWorkflow(ctx context.Context, request *UpdateWorkflowOptionsRequest) (WorkflowUpdateHandle, error) |
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.
UpdateWorkflow(ctx context.Context, request *UpdateWorkflowOptionsRequest) (WorkflowUpdateHandle, error) | |
UpdateWorkflow(ctx context.Context, options UpdateWorkflowOptions) (WorkflowUpdateHandle, error) |
Wonder if it is a "request" or "options", and since it will always be required, probably not value in accepting a pointer (I know we are inconsistent here). Even if it is a "request", then can probably remove the word "Options" from within. I don't have strong opinions here.
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.
Yeah i think we used request since that is what QueryWorkflowWithOptions
did. I can change it to not take a pointer.
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.
👍 I can see arguments for both Request
and Options
for the value of X
in UpdateWorkflowX
, but probably don't need both. (I have no strong opinion on which, I kinda like "options" but it's a very weak preference, your choice)
d0ad60c
to
d7bedd7
Compare
This PR makes multiple changes to the client experience around update:
UpdateWorkflowWithOptions
andUpdateWorkflow
to a single apiWaitForStage
a required parameter in updatecloses #1414
closes #1449
closes #1411
since this has multiple breaking changes feature tests are expected to fail until I make a separate branch