Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Before, we had
The whole separate "group" slot was confusing. It conflicted with the term "grouping variable", which describes
y
above, and it's a dangling slot oftarget()
.This PR cleans up and completes the idea. Now, we have tags, which are grouping variables added post-hoc.
Created on 2019-01-20 by the reprex package (v0.2.1)
Above,
x
andy
are implicit out-tags.from
is an explicit in-tag.to
andout
are explicit out-tags.The whole concept is intuitive and symmetric. Users can chain tags together to create much more complicated dependency graphs from individual calls to
drake_plan()
.Related
#233
Checklist
drake
's code of conduct, and I agree to follow its rules.testthat
unit tests totests/testthat
to confirm that any new features or functionality work correctly.devtools::check()