Move lintr out of Suggests #359
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hughjonesd
reviewed
Dec 12, 2025
Owner
hughjonesd
left a comment
hughjonesd
left a comment
There was a problem hiding this comment.
ok, I've simply left it out. Don't think I was using it anyway and would move to jarl.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for using {lintr}!
That said, I don't think the package actually uses it (there's no
lintr::usage in the package), so we can reduce the dependency web of {lintr} by moving it elsewhere in the DESCRIPTION to mark it as "this package uses {lintr} to keep up code quality". There's not really a standard way to do so, but something likeConfig/needs/developmentorConfig/wants/developmentfeel OK to me.