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
If grind.dart exports a file that defines a task, grinder will see that task. However, if that file in turn exports another file that defines a task, grinder won't see it. This makes it difficult to write libraries that provide tasks that users can include in their grind.dart via export (which is the only means available to do so as far as I know).
This has a few benefits:
* It allows us to dynamically choose task dependencies (so for example
the Linux standalone package can depend on the native executable
task when running on Linux).
* Similar tasks can be defined programmatically.
* Task names are decoupled from Dart function names, which in turn
allows us to avoid manually namespacing the package in favor of
encouraging it to be imported with a Dart namespace.
* It works around google/grinder.dart#337 and google/grinder.dart#338.
Declare tasks programatically rather than declaratively
This has a few benefits:
* It allows us to dynamically choose task dependencies (so for example
the Linux standalone package can depend on the native executable
task when running on Linux).
* Similar tasks can be defined programmatically.
* Task names are decoupled from Dart function names, which in turn
allows us to avoid manually namespacing the package in favor of
encouraging it to be imported with a Dart namespace.
* It works around google/grinder.dart#337 and google/grinder.dart#338.
If
grind.dart
exports a file that defines a task, grinder will see that task. However, if that file in turn exports another file that defines a task, grinder won't see it. This makes it difficult to write libraries that provide tasks that users can include in theirgrind.dart
viaexport
(which is the only means available to do so as far as I know).For example:
The text was updated successfully, but these errors were encountered: