You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would there be interest in providing a function that generates an explicit (e.g. defaults explicitly listed and commented) .lintr.R configuration. These could be pre-populated templates within the package or generated by users at runtime.
The motivation for this is that an explicit format makes it clear to new (and probably old) users what lints are going to be run and, if commentary is also supplied, what those lints do. Of course there are drawbacks to the explicit approach (e.g. a need to regenerate the file with new releases) but I think the option could be useful.
Some code I've been playing with is shared below. At the moment it is purely set to print out and comment all linters but there is no reason it couldn't handle customisation and NULLing of linters as with the other functions.
Would there be interest in providing a function that generates an explicit (e.g. defaults explicitly listed and commented)
.lintr.R
configuration. These could be pre-populated templates within the package or generated by users at runtime.The motivation for this is that an explicit format makes it clear to new (and probably old) users what lints are going to be run and, if commentary is also supplied, what those lints do. Of course there are drawbacks to the explicit approach (e.g. a need to regenerate the file with new releases) but I think the option could be useful.
Some code I've been playing with is shared below. At the moment it is purely set to print out and comment all linters but there is no reason it couldn't handle customisation and NULLing of linters as with the other functions.
I'm happy to pursue this further in a draft PR but no worries if not desirable / out of scope.
The text was updated successfully, but these errors were encountered: