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

idea: use_pipe()? #15

Closed
tidy-bot opened this issue Mar 2, 2017 · 3 comments
Closed

idea: use_pipe()? #15

tidy-bot opened this issue Mar 2, 2017 · 3 comments
Labels

Comments

@tidy-bot
Copy link

@tidy-bot tidy-bot commented Mar 2, 2017

Issue by ijlyttle
Sunday Jul 10, 2016 at 13:45 GMT
Originally opened as r-lib/devtools#1258


Given the emergence of the idea of Tidy API's, which encourages use of the pipe, could it be useful to provide a function use_pipe() that would create a pipe.R file like this? h/t @ramnathv here.

I see the plus side as making it easier to use "your" package functions not having to load magrittr explicitly.

I see a drawback (potentially) if every package exports the pipe, could that be messy/problematic? (Honestly, I don't know.)

Thoughts?

@tidy-bot
Copy link
Author

@tidy-bot tidy-bot commented Mar 2, 2017

Comment by hadley
Sunday Jul 10, 2016 at 14:24 GMT


I like it. As far as I know, there are no problems with everyone re-exporting the pipe.

@tidy-bot
Copy link
Author

@tidy-bot tidy-bot commented Mar 2, 2017

Comment by hadley
Sunday Jul 10, 2016 at 14:25 GMT


Also it might be worthwhile to let this simmer for a bit, with the aim of eventually becoming use_tidyverse() or similar.

@tidy-bot
Copy link
Author

@tidy-bot tidy-bot commented Mar 2, 2017

Comment by ijlyttle
Sunday Jul 10, 2016 at 15:48 GMT


Happy to let this simmer - if/when I can be of help, please let me know.

@hadley hadley removed the usethis label Aug 9, 2017
@hadley hadley closed this in c590e47 Aug 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants