-
Notifications
You must be signed in to change notification settings - Fork 183
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
lint_package('lintr') #47
Comments
Tim, First I agree with you about lintr passing its own linting. One of the reasons you are getting more lints than I would be is I have my default line length linter set to 120 rather than 80 characters. I am currently in the process of supporting per-project lint settings, which will clear up that issue. However there are still other lints which I need to fix in lintr. However these warnings you mentioned are disturbing to me. I have |
after a bit of futzing, and reading your note regarding 80 vs. 120 char lines, I'm reasonably confident that the non-line-length complaints are due to things (like .onLoad) that are baked into R. That said, here's my session info, and the pull request will be coming shortly (mostly just a bit of tidying and addition of names.lints / split.lints to ease exploration of output from lint_package).
|
Also Tim in terms of enforcing camelCase instead of snake_case the easiest way to do it is with lint_package(".",
linters = with_defaults(
object_camel_case_linter = NULL,
object_snake_case_linter
)
) Or to also only lint for lines over 120 lint_package(".",
linters = with_defaults(
object_camel_case_linter = NULL,
object_snake_case_linter,
line_length_linter(120)
)
) |
So since I haven't the foggiest idea what I'm doing (at the moment I'm trying to enforce camelCase instead of underscores_between_variable_name_bits, blah blah), I figured I'd start by linting lintr.
So some thoughts (which will turn into a pull request momentarily):
The text was updated successfully, but these errors were encountered: