-
Notifications
You must be signed in to change notification settings - Fork 133
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
Pipeline crosstab #34
Conversation
Needed crosstab.default to accept lists, expect_equal was also failing on the percent='all' test but shouldnt' have been.
Current coverage is 98.82%@@ master #34 diff @@
========================================
Files 9 9
Lines 151 170 +19
Methods 0 0
Messages 0 0
Branches 0 0
========================================
+ Hits 151 168 +17
- Misses 0 2 +2
Partials 0 0
|
Wow! Wizardry. I don't entirely follow and will need to do some reading to 100% understand, but it works great. The one question I have now is, I see when I start typing "crosstab" in RStudio I get "crosstab.data.frame" and "crosstab.default" suggested. Is it standard to export those? Is it possible some users will want to call them directly? I don't immediately see a purpose to exporting them. |
Your probably right regarding exporting them. I'll double check tomorrow and make changes as necessary. |
I don't think you generally export the functions that only do method dispatch. I think those stay internal |
This creates an S3 generic for crosstab as well as default and
data.table
methods. Thecrosstab
is now pipeable. One side effect of this is I had to allowlist
objects as acceptable objects forvec1
andvec2
parameters in thecrosstab.default
. (Essentially as a way to deal with NSE in both thecrosstab.data.frame
andcrosstab.default
methods). I've updated the tests and the package is currently passing R CMD CHECK on my MBP.