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

Reconsider re-exports from rlang #6802

Open
DavisVaughan opened this issue Mar 21, 2023 · 1 comment
Open

Reconsider re-exports from rlang #6802

DavisVaughan opened this issue Mar 21, 2023 · 1 comment
Labels
breaking change ☠️ API change likely to affect existing code feature a feature request or enhancement rlang 🔬

Comments

@DavisVaughan
Copy link
Member

DavisVaughan commented Mar 21, 2023

Can we start to un-export any of these https://github.com/tidyverse/dplyr/blob/main/R/utils-tidy-eval.R?

Also, should we un-export .data? It doesn't belong on that help page, as noted in #6801. We also don't export .env from dplyr, but those two are very closely related, and right now you can do ?dplyr::.data but not ?dplyr::.env.

@DavisVaughan DavisVaughan added feature a feature request or enhancement breaking change ☠️ API change likely to affect existing code rlang 🔬 labels Nov 3, 2023
@mkoohafkan
Copy link

I came here to see if the was an open issue on adding .env as a re-export for {dplyr}. I have a few packages where the only thing I need to import from {rlang} is .env, so being able to skip that and just import both .data and .env from {dplyr} would be mildly more convenient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change ☠️ API change likely to affect existing code feature a feature request or enhancement rlang 🔬
Projects
None yet
Development

No branches or pull requests

2 participants