Set ParentClosePolicy default value #481
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mfateev
requested changes
Jun 27, 2020
common/enums/defaults.go
Outdated
|
|
||
| func SetDefaultParentClosePolicy(f *enumspb.ParentClosePolicy) { | ||
| if *f == enumspb.PARENT_CLOSE_POLICY_UNSPECIFIED { | ||
| *f = enumspb.PARENT_CLOSE_POLICY_ABANDON |
Member
There was a problem hiding this comment.
The default should be TERMINATE.
How do I determine default looking at the proto definition?
mfateev
approved these changes
Jun 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
ParentClosePolicyon request is set toTerminateif case if not specified.WorkflowIdReusePolicyis also set to default value inhandleDecisionStartChildWorkflow.Why?
taskProcessorreturns error ifParentClosePolicyorWorkflowIdReusePolicyis not specified on request and there is no validation logic for it.How did you test it?
Run all tests (including Go SDK integration tests).
Potential risks
No risks.