We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be nice if map_at() could incorporate tidyselect functions:
map_at()
library(purrr) library(tidyselect) map_at_two <- function(.x, .at, .f, ...){ outvars <- vars_select(.vars = names(.x), .at) map_at(.x, outvars, .f, ...) } x <- list(a = "b", b = "c", aa = "bb") map_at_two(x, contains("a"), toupper) #> $a #> [1] "B" #> #> $b #> [1] "c" #> #> $aa #> [1] "BB" map_at_two(x, 1, toupper) #> $a #> [1] "B" #> #> $b #> [1] "c" #> #> $aa #> [1] "bb" map_at_two(x, "a", toupper) #> $a #> [1] "B" #> #> $b #> [1] "c" #> #> $aa #> [1] "bb" x <- list("b", "c", "bb") map_at_two(x, contains("a"), toupper) #> Error: No tidyselect variables were registered <sup>Created on 2019-01-02 by the [reprex package](https://reprex.tidyverse.org) (v0.2.1)</sup>
{tidyselect} has purrr as a dependencies, so it might imply that {purrr} functions used in {tidyselect} have to be rewritten.
{tidyselect}
{purrr}
The text was updated successfully, but these errors were encountered:
Sorry, purrr is unlikely to gain any NSE features. The right way to do it would be to take a vars() list by the way, as in mutate_at() etc.
vars()
mutate_at()
Sorry, something went wrong.
@lionel- just in case, this is the issue I've referred to tonight :)
Working on this one today
Successfully merging a pull request may close this issue.
It would be nice if
map_at()
could incorporate tidyselect functions:{tidyselect}
has purrr as a dependencies, so it might imply that{purrr}
functions used in{tidyselect}
have to be rewritten.The text was updated successfully, but these errors were encountered: