Skip to content
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

Extreme type safety! #9

Closed
Tyler-Keith-Thompson opened this issue Apr 26, 2021 · 0 comments · Fixed by #10
Closed

Extreme type safety! #9

Tyler-Keith-Thompson opened this issue Apr 26, 2021 · 0 comments · Fixed by #10
Labels
enhancement New feature or request

Comments

@Tyler-Keith-Thompson
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

Workflow has some sort of type safety at the moment and that's very helpful. We can take it much, much farther with the notion that compile-time errors are preferred.

Describe the solution you'd like

For example every FlowRepresentable can declare both an Input and Output, then when you create a workflow you can enforce (with a fluent API) that the next thing being presented has the same kind of Input that the last thing outputs.

Describe alternatives you've considered

We could not have type safety and just make everyone deal with "Any" for the rest of their lives, but that seems cruel.

Additional context

It's already done.....mostly.

@Tyler-Keith-Thompson Tyler-Keith-Thompson linked a pull request Apr 27, 2021 that will close this issue
18 tasks
@Richard-Gist Richard-Gist added this to the Orchestration Engine milestone Apr 28, 2021
@Richard-Gist Richard-Gist added the enhancement New feature or request label Apr 28, 2021
@Tyler-Keith-Thompson Tyler-Keith-Thompson mentioned this issue May 3, 2021
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants