-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add run_process #307
base: draft
Are you sure you want to change the base?
Add run_process #307
Conversation
See comment on other issue: currently not in favor of this as a solution to avoid allowing parameters for process_id. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look okay to us.
a devil's advocate argument against this process: I think you lose the ability to statically check/validate your process graph because the output schema of run_process is only known at run time. This might be annoying in several places: visualization of process graph (e.g. in web editor), in clients that use output schemas to help building a process graph , the |
Yes, but checking it in the JS tooling shows that this is equally annoying as allowing variable for |
Proposal for solving Open-EO/openeo-api#413 in a non-breaking way.
Similar functions in other programming languages:
let func = 'max'; Math[func](123, 321)