-
Notifications
You must be signed in to change notification settings - Fork 36
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
Add workflow stack
command
#457
Conversation
case "not_completed_cleanly": | ||
queryRejectCond = enums.QUERY_REJECT_CONDITION_NOT_COMPLETED_CLEANLY | ||
default: | ||
return fmt.Errorf("invalid query reject condition: %v, valid values are: 'not_open', 'not_completed_cleanly'", rejectCondition) |
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.
In theory with how string-enum works this should never get this far, but I support the default anyways
return fmt.Errorf("invalid query reject condition: %v, valid values are: 'not_open', 'not_completed_cleanly'", rejectCondition) | ||
} | ||
|
||
result, err := cl.WorkflowService().QueryWorkflow(cctx, &workflowservice.QueryWorkflowRequest{ |
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.
Mentioned in other review, and don't have to change, but this could use the high-level QueryWorkflowWithOptions
(changing buildRawInputPayloads
to buildRawInput
), but no big difference.
What was changed
Added
workflow stack
command. Looks just likequery
output. In the future we should probably do a better job of formatting this, but it's not simple. Probably makes the most sense with enhanced trace.Why?
Part of cli rewrite.
Checklist
Closes
How was this tested: