-
Notifications
You must be signed in to change notification settings - Fork 218
Improve WorkflowBuilder
API
#2284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Milestone
Comments
see also: #2256 (comment) |
metacosm
added a commit
that referenced
this issue
Aug 21, 2024
Fixes #2284 Signed-off-by: Chris Laprun <[email protected]>
metacosm
added a commit
that referenced
this issue
Aug 30, 2024
Fixes #2284 Signed-off-by: Chris Laprun <[email protected]>
metacosm
added a commit
that referenced
this issue
Sep 19, 2024
* feat: explicit node configuration in WorkflowBuilder Fixes #2284 Signed-off-by: Chris Laprun <[email protected]> * refactor: rename more appropriately Signed-off-by: Chris Laprun <[email protected]> --------- Signed-off-by: Chris Laprun <[email protected]>
csviri
pushed a commit
that referenced
this issue
Sep 20, 2024
* feat: explicit node configuration in WorkflowBuilder Fixes #2284 Signed-off-by: Chris Laprun <[email protected]> * refactor: rename more appropriately Signed-off-by: Chris Laprun <[email protected]> --------- Signed-off-by: Chris Laprun <[email protected]>
metacosm
added a commit
that referenced
this issue
Oct 10, 2024
* feat: explicit node configuration in WorkflowBuilder Fixes #2284 Signed-off-by: Chris Laprun <[email protected]> * refactor: rename more appropriately Signed-off-by: Chris Laprun <[email protected]> --------- Signed-off-by: Chris Laprun <[email protected]>
metacosm
added a commit
that referenced
this issue
Nov 5, 2024
* feat: explicit node configuration in WorkflowBuilder Fixes #2284 Signed-off-by: Chris Laprun <[email protected]> * refactor: rename more appropriately Signed-off-by: Chris Laprun <[email protected]> --------- Signed-off-by: Chris Laprun <[email protected]>
metacosm
added a commit
that referenced
this issue
Nov 6, 2024
* feat: explicit node configuration in WorkflowBuilder Fixes #2284 Signed-off-by: Chris Laprun <[email protected]> * refactor: rename more appropriately Signed-off-by: Chris Laprun <[email protected]> --------- Signed-off-by: Chris Laprun <[email protected]>
csviri
pushed a commit
that referenced
this issue
Nov 13, 2024
* feat: explicit node configuration in WorkflowBuilder Fixes #2284 Signed-off-by: Chris Laprun <[email protected]> * refactor: rename more appropriately Signed-off-by: Chris Laprun <[email protected]> --------- Signed-off-by: Chris Laprun <[email protected]>
metacosm
added a commit
that referenced
this issue
Nov 19, 2024
* feat: explicit node configuration in WorkflowBuilder Fixes #2284 Signed-off-by: Chris Laprun <[email protected]> * refactor: rename more appropriately Signed-off-by: Chris Laprun <[email protected]> --------- Signed-off-by: Chris Laprun <[email protected]>
metacosm
added a commit
that referenced
this issue
Nov 20, 2024
* feat: explicit node configuration in WorkflowBuilder Fixes #2284 Signed-off-by: Chris Laprun <[email protected]> * refactor: rename more appropriately Signed-off-by: Chris Laprun <[email protected]> --------- Signed-off-by: Chris Laprun <[email protected]>
metacosm
added a commit
that referenced
this issue
Nov 27, 2024
* feat: explicit node configuration in WorkflowBuilder Fixes #2284 Signed-off-by: Chris Laprun <[email protected]> * refactor: rename more appropriately Signed-off-by: Chris Laprun <[email protected]> --------- Signed-off-by: Chris Laprun <[email protected]>
csviri
pushed a commit
that referenced
this issue
Dec 6, 2024
* feat: explicit node configuration in WorkflowBuilder Fixes #2284 Signed-off-by: Chris Laprun <[email protected]> * refactor: rename more appropriately Signed-off-by: Chris Laprun <[email protected]> --------- Signed-off-by: Chris Laprun <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should have an intermediate API to configure nodes in the workflow in a type-safe and less confusing way. Right now, things are implicitly done, relying on the order of method calls. While what is going on can easily be figured out by looking at the builder's implementation, we should make things type-safe and error-proof via the API.
The text was updated successfully, but these errors were encountered: