-
Notifications
You must be signed in to change notification settings - Fork 186
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
Suggestion: ignore linters due to imported functions #191
Comments
An alternative is to use Excluding functions imported into the package NAMESPACE is possible of course, but lintr currently works on a file a time and does not handle package structure at all, so it would require some changes in how things work. |
@ThierryO I like your suggestion! |
@jimhester Note that in the second paragraph Hadley writes:
Would you accept a pull request which takes into account the imports from |
I think what @fangly Suggested makes sense, if the |
Come to think of it, if that's of the objects_linter.R (name length, camel case, etc) that we are talking about, there may be a better strategy. I do also get a lot of lints from function calls, dataframe accesses, etc that I did not create. |
I updated my |
Fixed in #214 |
Since there is no common coding style in R, importing functions from other packages often results in a clash of coding styles. Currently we have to
#nolint
the offending functions, which is a bit tedious. All imported functions are listed inNAMESPACE
so that would be nice place to look for the exceptions.The text was updated successfully, but these errors were encountered: