You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, a really nice package! Thanks for that. 🙌🏼
Now, to the actual issue...
Since the entire point of defining "as code" is to be able to reuse chunks of definitions. I feel like then types need to be exported for each chunk that can be reused.
For example, there is no exported type for a step, and even trying to do various TypeScript acrobatics to infer the type, it won't work, since the step type is a complicated union.
I think each composable type needs to be exported.
At least:
Step
Job
Workflow
Or factory functions, like createWorkflow.
At the same time, there are many types that are exported, which are not needed.
The text was updated successfully, but these errors were encountered:
First of all, a really nice package! Thanks for that. 🙌🏼
Now, to the actual issue...
Since the entire point of defining "as code" is to be able to reuse chunks of definitions. I feel like then types need to be exported for each chunk that can be reused.
For example, there is no exported type for a step, and even trying to do various TypeScript acrobatics to infer the type, it won't work, since the step type is a complicated union.
I think each composable type needs to be exported.
At least:
Or factory functions, like
createWorkflow
.At the same time, there are many types that are exported, which are not needed.
The text was updated successfully, but these errors were encountered: