Conflicts within the tidyverse are not consistently called out #26
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: