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.

Sign up for GitHub

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

Jump to bottom

Use {conflicted} to avoid conflict warnings? #1172

Open
IndrajeetPatil opened this issue Jun 28, 2022 · 2 comments
Open

Use {conflicted} to avoid conflict warnings? #1172

IndrajeetPatil opened this issue Jun 28, 2022 · 2 comments
Labels
documentation Improvements or additions to documentation
Milestone
book

Comments

@IndrajeetPatil
Copy link
Contributor

I learned today that we can also load {conflicted} to avoid those warnings, at least in reprexes: mgirlich/tibblify#97. Does that also apply to vignettes?

Originally posted by @krlmlr in #1098 (comment)
@IndrajeetPatil IndrajeetPatil mentioned this issue Jun 28, 2022
Merged
@IndrajeetPatil
Copy link
Contributor Author

@krlmlr This is only to suppress warnings about conflicts in the vignettes, right?

Why can't we just use warning = FALSE, message = FALSE chunk options for chunks where we are loading libraries, instead of getting a whole new dependency like {conflicted}?

@krlmlr krlmlr added the documentation Improvements or additions to documentation label Jul 6, 2022
@krlmlr
Copy link
Collaborator

krlmlr commented Aug 20, 2023

Because conflicted also gives an error when it's not super-clear which function is referred to.

@krlmlr krlmlr added this to the book milestone Aug 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation
Milestone
book
Development

No branches or pull requests
2 participants
@krlmlr @IndrajeetPatil