Skip to content

Conversation

@Merott
Copy link

@Merott Merott commented May 26, 2014

A flow that is marked as passive, will not produce the warning
"No destination specified; this entire flow went nowhere."

If a task is set to passive, but a merge or dest option has
been specified, the build will stop.

A flow that is marked as passive, will not produce the warning
"No destination specified; this entire flow went nowhere."

If a task is set to passive, but a `merge` or `dest` option has
been specified, the build will stop.
@Merott
Copy link
Author

Merott commented May 26, 2014

This is useful for flows like karma-single-run, which is not meant to have a destination, and helps keep the build output clean from false warnings.

Merott added a commit to Merott/spell-karma that referenced this pull request May 26, 2014
Stop the warning shown for no destination specified.
Requires: ngbp/warlock#8
Merott added a commit to Merott/spell-karma that referenced this pull request May 26, 2014
Stop the warning shown for no destination specified.
Requires: ngbp/warlock#8
Merott added a commit to Merott/spell-webapp that referenced this pull request May 26, 2014
Stop the warning shown for no destination specified.
Requires: ngbp/warlock#8
Merott added a commit to Merott/spell-coffeescript that referenced this pull request May 26, 2014
Stop the warning shown for no destination specified.
Requires: ngbp/warlock#8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant