Show how targets were expanded with wildcards #461
Merged
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
trace
argument toevaluate_plan()
to optionally add indicator columns to show which targets got expanded/evaluated with which wildcard values.always_rename
argument torename
inevaluate_plan()
.rename
argument toexpand_plan()
.(1) solves #376 because it allows easier custom filtering for later gathering. @tmastny, I know this is not quite what you asked for, but it makes custom gathering easier while preserving the flexibility and design patterns of
drake
.(1) also opens up new visualization possibilities because it provides natural groupings for targets.
Related GitHub issues
gather/reduce_plan
#376Checklist
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()