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
Currently, tasks are registered in a global scope managed by quake. By assigning variables to tasks, perhaps storing metadata inside of a custom value, we can get scope resolution and shadowing of tasks for free.
This would also allow for referencing tasks with other commands or as values (e.g. $build.artifacts). This could alternatively be implemented with the existing global $quake variable (e.g. $quake.tasks.build.artifacts).
The text was updated successfully, but these errors were encountered:
Currently, tasks are registered in a global scope managed by quake. By assigning variables to tasks, perhaps storing metadata inside of a custom value, we can get scope resolution and shadowing of tasks for free.
This would also allow for referencing tasks with other commands or as values (e.g.
$build.artifacts
). This could alternatively be implemented with the existing global$quake
variable (e.g.$quake.tasks.build.artifacts
).The text was updated successfully, but these errors were encountered: