-
Notifications
You must be signed in to change notification settings - Fork 4
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
warning from {lintr}
workflow in [namespace_lintr]
#119
Comments
It looks like epiparameter and epidemics and not properly installed during the lintr check. I'll look into it.
|
thank you @Bisaloo this is the only the list of packages highlighted as sources of warning are:
|
also only package highlighted is |
@Bisaloo, in order to give it more time to investigate the source of the issue, we can temporarily replace |
The simplest option at this time is probably to disable this linter altogether by editing the
|
got it, just found the .lintr file! I can proceed by:
but keeping this issue open for further investigation or decision. happy to read your suggestions about this |
following suggestion in #119 (comment)
following suggestion in #119 (comment)
following suggestion in epiverse-trace/tutorials#119 (comment)
closing as solved |
In #104 from workflow in https://github.com/epiverse-trace/tutorials/actions/runs/7699737505/job/20982024773?pr=104 to line:
tutorials/episodes/read-delays.Rmd
Lines 187 to 190 in a253dac
I'm getting this
{lintr}
warningSome thoughts:
epiparameter
is called and installed from therenv.lock
. Where doeslintr
expect to find dependencies or if a package is installed?{package}
andfunction()
notation #25. should we adapt tolintr
? or adaptlintr
to some of our features?tagging @Bisaloo since this is related with #96
The text was updated successfully, but these errors were encountered: