-
Notifications
You must be signed in to change notification settings - Fork 187
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
export xp_call_name() for downstream use #2096
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2096 +/- ##
=======================================
Coverage 99.65% 99.65%
=======================================
Files 117 117
Lines 5158 5162 +4
=======================================
+ Hits 5140 5144 +4
Misses 18 18
|
Wondering about if the name is "nice" for exporting.
|
No. Here's the 3 packages (including {lintr}) on CRAN with any functions starting with
For packages using
AFAIK, no. The only other CRAN package mentioning "XPath" in its title is {selectr}, which is for translating CSS queries to XPath (and not the other way around). https://cran.r-project.org/web/packages/available_packages_by_name.html There are many more packages that use "XPath" somewhere in their sources, I didn't see any pattern emerge when glancing through the results here: https://github.com/search?q=org%3Acran+language%3Ar+%22xpath%22&type=code Here are all CRAN functions using "xpath"... still not solid pattern: |
Thanks for doing the research. WDYT about |
Not strongly opposed. Main worry is confusion vs {xml2} functions. Esp. if this grows to be a family of exported functions (there are already a few more private We also use |
Closes #2023