-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
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
detect() doesn't seem to take a logical vector #348
Comments
i understood the docs as |
No, you could be right... I guess that would mean that the documentation should be updated if Thanks for the suggestion... Can it be |
It seems to work so. As far as i understand the error comes when |
It seems like x <- list(
list(1, foo = FALSE),
list(2, foo = TRUE),
list(3, foo = TRUE)
)
detect(x, "foo")
detect_index(x, "foo") |
So they are documented with the right semantics. Closes tidyverse#348
So they are documented with the right semantics. Closes tidyverse#348
@david-jankoski Thanks, I'll leave it here. Appreciate the comments thought And thanks @lionel-, got it. |
After changing detect from .p to .f, the documentation still refers to .p for ellipsis .f | A function, specified in one of the following ways: small thing but perhaps worth changing? |
Documentation reads:
But...
Saw, #330 and see that there might be better functions, but I'm still curious...
A simple work around:
Thanks
The text was updated successfully, but these errors were encountered: