Skip to content
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

Feature Request: tidyverse_conflicts() message with "conflicted Package Info" #218

Closed
jtelleriar opened this issue Jan 15, 2020 · 0 comments
Labels
feature a feature request or enhancement

Comments

@jtelleriar
Copy link

jtelleriar commented Jan 15, 2020

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.
@batpigandme batpigandme added the feature a feature request or enhancement label Jan 15, 2020
@hadley hadley closed this as completed in 53a1843 Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature a feature request or enhancement
Projects
None yet
Development

No branches or pull requests

2 participants