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
Search for duplicates among the existing issues, both open and closed.
Advanced users: verify that the bug still persists in the current development version (i.e. remotes::install_github("ropensci/drake")) and mention the SHA-1 hash of the Git commit you install.
Description
This is related to, but I think distinct from #1076.
When using the output of a dynamic target in a subsequent target, I get a hash of class drake_dynamic instead of the expected output that is a list of values.
A dynamic (parent) target is just a vector of hashes by design. It's part of the implementation that makes it all work. If you use a dynamic target in the command for another target, what drake thinks you are really saying is that you want to iterate over the sub-targets. So the dynamic target should usually also go in map(), cross() or group(). In other words, downstream targets of dynamic targets should also be dynamic, except when you want to explicitly promote a group of sub-targets with readd().
Prework
drake
's code of conduct.remotes::install_github("ropensci/drake")
) and mention the SHA-1 hash of the Git commit you install.Description
This is related to, but I think distinct from #1076.
When using the output of a dynamic target in a subsequent target, I get a hash of class
drake_dynamic
instead of the expected output that is a list of values.Reproducible example
Created on 2019-12-04 by the reprex package (v0.3.0)
Session info
Expected result
readd(baz)$a == readd(bat)$b
Session info
End the reproducible example with a call to
sessionInfo()
in the same session (e.g.reprex(si = TRUE)
) and include the output.The text was updated successfully, but these errors were encountered: