Flow class is a decorator of WorkflowDefinition class.
There are some scenarios (for example, accessing the list of scheduled instances) where will be useful to access the WorkflowDefinition wrapped by the Flow class.
I propose, rather than adding those method and call the definition internally, to expose directly WorkflowDefinition by making this method public
This makes sense because, after all, WorlfkowDefinition is injectable, so there is not really a big deal making it public in Flow.
By the way, talking about method scope, init method in Flow class should be probably not public.
Flow class is a decorator of WorkflowDefinition class.
There are some scenarios (for example, accessing the list of scheduled instances) where will be useful to access the WorkflowDefinition wrapped by the Flow class.
I propose, rather than adding those method and call the definition internally, to expose directly WorkflowDefinition by making this method public
This makes sense because, after all, WorlfkowDefinition is injectable, so there is not really a big deal making it public in Flow.
By the way, talking about method scope, init method in Flow class should be probably not public.