Conversation
0.5.0 was spitting out warnings related to rubocop deprecations [skip changelog]
erb_lint complains if you invoke it with `erblint`. This silences that warning.
aduth
approved these changes
Dec 6, 2024
Contributor
aduth
left a comment
aduth
left a comment
There was a problem hiding this comment.
Nice, the previous inconsistency between erblint, erb-lint, and erb_lint always tripped me up, nice that they've consolidated 👍
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
erb_lint 0.5.0 was starting to emit warnings about Rubocop deprecations. Updating to 0.7.0 silences those warnings. It looks like they changed the preferred config file name and invocation method, so I've updated those as well to avoid additional warnings.