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
It would be nice, and easily implementable, that when executing tidyverse_conflicts() function, a message is also included that "spreads the word" about "conflicted" R Package, as an alternative (and useful) conflict resolution strategy.
Current behavior is:
> library(tidyverse)
-- Attaching packages --------------------------------------- tidyverse 1.3.0 --
v ggplot2 3.2.1 v purrr 0.3.3
v tibble 2.1.3 v dplyr 0.8.3
v tidyr 1.0.0 v stringr 1.4.0
v readr 1.3.1 v forcats 0.4.0
-- Conflicts ------------------------------------------ tidyverse_conflicts() --
x dplyr::filter() masks stats::filter()
x dplyr::lag() masks stats::lag()
My proposal is:
-- Conflicts ------------------------------------------ tidyverse_conflicts() --
x dplyr::filter() masks stats::filter()
x dplyr::lag() masks stats::lag()
-- Strict Conflict Resolution Strategy: Use 'conflicted' R Package for making every conflict between loaded package functions an error, and force you to choose which function to use.
Or:
-- Conflicts ------------------------------------------ tidyverse_conflicts() --
x dplyr::filter() masks stats::filter()
x dplyr::lag() masks stats::lag()
-- For a Strict Conflict Resolution Strategy: Use 'conflicted' R Package.
The text was updated successfully, but these errors were encountered:
It would be nice, and easily implementable, that when executing tidyverse_conflicts() function, a message is also included that "spreads the word" about "conflicted" R Package, as an alternative (and useful) conflict resolution strategy.
Current behavior is:
My proposal is:
Or:
The text was updated successfully, but these errors were encountered: