Release erb_lint v0.7.0 #382
Merged
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
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.
There are useful unreleased fixes and features, so cutting a release makes sense to me.
Main changes are:
Consistently use the
erb_lintname, instead oferb-lintorerblint. The old names are still supported, but will be removed in a future release.Standardize repo name to
erb_lint#360Rename the cache directory to match the new name. Your first build will rebuild it from scratch.
Rename
CACHE_DIRECTORYto.erb_lint_cache. #380Don't use rexml for the JUnit formatter
Don't use rexml for the JUnit formatter #374
Allow laquo and raquo in HardCodedString linter
Allow laquo and raquo in HardCodedString linter #355
Don't use possibly deprecated RuboCop api
Don't use possibly deprecated RuboCop api #375