We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In GitLab by @JonathanMace on Sep 16, 2023, 24:49
It is reasonable for a workflow spec to provide multiple constructors for a service, e.g. with expanded configuration options.
The current workflow spec parsing logic does not support multiple constructors, but there is no fundamental reason preventing us from doing so.
One option is to allow the workflow spec to state exactly which constructor to invoke
Another option is to pattern-match the constructor based on the args provided in the wiring spec.
The text was updated successfully, but these errors were encountered:
JonathanMace
No branches or pull requests
In GitLab by @JonathanMace on Sep 16, 2023, 24:49
It is reasonable for a workflow spec to provide multiple constructors for a service, e.g. with expanded configuration options.
The current workflow spec parsing logic does not support multiple constructors, but there is no fundamental reason preventing us from doing so.
One option is to allow the workflow spec to state exactly which constructor to invoke
Another option is to pattern-match the constructor based on the args provided in the wiring spec.
The text was updated successfully, but these errors were encountered: