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
Such a transit task is confusing, as a developer can easily forget about this hack, and later on, when he finds no "transit" tasks in package.json he will be tempted to remove the task "Note that this hack is done in a json file where we cannot introduce a comment to clarify".
He might use a task name that's not unique enough and will be created in the future, thus becoming a useless dependency
Proposal
Instead of using a fake task "Transit Node", we can use a feature flag like "useDependencyAwareParallelism"
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Goals
Non-goals
No response
Background
In "Dependent tasks that can be ran in parallel", The user needs to create a transit node "fake task" to be able to run in parallel.
The problem is that
package.json
he will be tempted to remove the task "Note that this hack is done in a json file where we cannot introduce a comment to clarify".Proposal
Instead of using a fake task "Transit Node", we can use a feature flag like "useDependencyAwareParallelism"
Beta Was this translation helpful? Give feedback.
All reactions