specification
specification copied to clipboard
serverlessworkflow
Enforce action name
What would you like to be added:
The name of actions to be required.
Why is this needed: The name is a human, comprehensible way of working. When reviewing the activities of a workflow, knowing that "Action[2]" was a success doesn't really speak to the user. It requires to have the definition under the eyes, count the actions to find the one we are speaking about. Having it named will improve readability and maintainability of workflows and their activities.
+1
But honestly, implementations can compose the action description using the definition of the given action. But I agree that a required name could be more accessible for debug purposes.
This also applies to other item types like branch.
A name should be unique within the scope of its parent but not the whole workflow.
As agreed in the meeting call, within the same state, we should guarantee action uniqueness
Yes branch names are also going to be enforced as part of error handling updates.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Seems this suggested hasn't moved to the specification yet. Should we update the spec?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.