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
Currently this produces an error (could not find function "efficient.cars") but I think it would be very useful if we were able to do this. There is a simple fix,
but this means that I often have to switch -> and %>% during development (every time, the last step in a chain changes) and this creates unnecessary friction.
I think it would be logically consistent to allow piping into a variable since we also can pipe from a variable. Thanks for considering this and sorry if this has been discussed previously.
The text was updated successfully, but these errors were encountered:
tmalsburg
changed the title
Feature request: allow variable name at the end of a chain
Feature request: allow variable at the end of a chain
Feb 18, 2017
tmalsburg
changed the title
Feature request: allow variable at the end of a chain
Feature request: allow variable as the end of a chain
Feb 18, 2017
I think this belongs in magrittr not dplyr. At any rate it isn’t currently possible because of the reason stated in the error message: if the last identifier in a pipe chain is a name, it’s interpreted as a function name. That is, … %>% foo is equivalent to … %>% foo().
It would be convenient to be able to pipe the results of a processing chain into a variable as in the following example:
Currently this produces an error (
could not find function "efficient.cars"
) but I think it would be very useful if we were able to do this. There is a simple fix,but this means that I often have to switch
->
and%>%
during development (every time, the last step in a chain changes) and this creates unnecessary friction.I think it would be logically consistent to allow piping into a variable since we also can pipe from a variable. Thanks for considering this and sorry if this has been discussed previously.
The text was updated successfully, but these errors were encountered: