-
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
keyword_quote_linter for unnecessary quoting #2030
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2030 +/- ##
=======================================
Coverage 99.61% 99.62%
=======================================
Files 115 116 +1
Lines 4983 5049 +66
=======================================
+ Hits 4964 5030 +66
Misses 19 19
|
|
Thanks for checking. Are you suggesting we shouldn't use |
I'm suggesting to fix the comment. |
oh, but that's what I meant -- 1 if there's a match, 0 if not, so |
The part about xml_child is wrong. It's simply not vectorized over nodesets so it would return the first child of the first match instead of the first child for each element in the resultset, and error if the resultset is empty. |
Ohh I get you now. even better. |
@@ -8,6 +8,20 @@ length_levels_linter() | |||
} | |||
\description{ | |||
\code{length(levels(x))} is the same as \code{nlevels(x)}, but harder to read. | |||
} | |||
\examples{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder how that slipped...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I must have forgotten to roxygenize()
after adding the examples in the other PR...
Continuing on with #884.
There are a few customizations/options we could add, LMK if we should do those here or in follow-up issues.