update lintr config for lintr >= 2 #294
Merged
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.
Prework
Related GitHub issues and pull requests
snake_case_linter
andcamel_case_linter
Summary
Please explain the purpose and scope of your contribution.
The package was set to use CRAN {lintr} (ie, >=v2)
snake_case_linter
andcamel_case_linter
were originally NULL-ed out (deactivated) in the{targets} .lintr config.
But, these linters were removed from lintr's default-linter set prior to
lintr v2 (so NULLing them in the config doesn't actually do anything).
In fact, the functions are being deprecated.
Hence I removed any mention of these linters from the targets .lintr.
Note that
snake_case_linter
/camel_case_linter
are now implemented aspart of
object_name_linter()
, but that the latter was already deactivated inthe {targets} .lintr config.