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
{{ message }}
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.
With the addition of #20, and others like it that will follow, there will come a time when we want to programmatically run tasks, without manually clicking the “run task” button.
Supporting this would make usage of Automaat more streamlined and it allows to get results faster.
The biggest blocker for this feature is that you cannot be sure that a task won’t mutate state or have other side-effects that are unexpected.
One way to tackle this would be to add a special flag on tasks (or steps, tbd), that’s signals wether a task is a query or a mutation.
If a task is a query (and should thus be side-effect free), it can be programmatically run.
There are still lots of design considerations to make on this, but creating this tracking issue is at least a step towards solving this.
The text was updated successfully, but these errors were encountered:
With the addition of #20, and others like it that will follow, there will come a time when we want to programmatically run tasks, without manually clicking the “run task” button.
Supporting this would make usage of Automaat more streamlined and it allows to get results faster.
The biggest blocker for this feature is that you cannot be sure that a task won’t mutate state or have other side-effects that are unexpected.
One way to tackle this would be to add a special flag on tasks (or steps, tbd), that’s signals wether a task is a query or a mutation.
If a task is a query (and should thus be side-effect free), it can be programmatically run.
There are still lots of design considerations to make on this, but creating this tracking issue is at least a step towards solving this.
The text was updated successfully, but these errors were encountered: