We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
namespace_imports
object_name_linter
I think the namespace one is actually a legit bug. namespace_imports is only called here:
https://github.com/jimhester/lintr/blob/fa05ceb2bf967ddad9230e25879b95084c80b0dc/R/object_name_linters.R#L57
without an argument. the default is to run find_package() (again without argument), but there's no default, so normalizePath always fails:
find_package()
normalizePath
https://github.com/jimhester/lintr/blob/fa05ceb2bf967ddad9230e25879b95084c80b0dc/R/lint.R#L287
In namespace_imports this error happens within tryCatch so it just returns NULL.
tryCatch
NULL
I'm not sure the intended behavior but certainly the above is not it 😃
Originally posted by @MichaelChirico in #639 (comment)
The text was updated successfully, but these errors were encountered:
fix and test namespace_imports() in object_name_linter
a587d3f
fixes #642 also increases coverage of R/namespace.R to 100%
Successfully merging a pull request may close this issue.
I think the namespace one is actually a legit bug.
namespace_imports
is only called here:https://github.com/jimhester/lintr/blob/fa05ceb2bf967ddad9230e25879b95084c80b0dc/R/object_name_linters.R#L57
without an argument. the default is to run
find_package()
(again without argument), but there's no default, sonormalizePath
always fails:https://github.com/jimhester/lintr/blob/fa05ceb2bf967ddad9230e25879b95084c80b0dc/R/lint.R#L287
In
namespace_imports
this error happens withintryCatch
so it just returnsNULL
.I'm not sure the intended behavior but certainly the above is not it 😃
Originally posted by @MichaelChirico in #639 (comment)
The text was updated successfully, but these errors were encountered: