-
Notifications
You must be signed in to change notification settings - Fork 292
Conflicts within the tidyverse are not consistently called out #26
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
Comments
Oooooooh, that's because jsonlite is a tidyverse package, so the conflict is deliberately excluded. |
Also |
The |
Closed
Also |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am specifically thinking of
jsonlite::flatten()
.tidyverse then jsonlite: we're notified that
jsonlite::flatten()
maskspurrr::flatten()
. But not reported as a conflict.jsonlite then tidyverse: we don't learn that
purrr::flatten()
masksjsonlite::flatten()
. Still not reported as a conflict.jsonlite then purrr: we learn that
purrr::flatten()
masksjsonlite::flatten()
.The text was updated successfully, but these errors were encountered: