Details
-
Story
-
Status: Open
-
Trivial
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
The built-in workflows are not stored on the service model's workflow field.
This can make sense in some ways, but can also cause awkward behavior, such as having an empty list returned when listing workflows in the CLI for a service which has no custom workflows.
It might be better to partially or fully push the built-in workflows into the service model's workflows field for it to be more whole.
This could also simplify some code in WorkflowRunner as there'd be no need to separate the cases of custom and built-in workflows anymore (except for, possibly, when referring to the workflow implementation)