Added CLI option to enable and clear the cache 🧣 #17
Conversation
This file contains 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
Both eslint and stylelint support a cache which can be used to only lint files which have changed. This can speed up the linting process which is important when lint tasks are run in pre-commit hooks. Having an option to clear the cache is also important. Although users could just delete the cache files, doing so via the CLI is easy and acts as a reminder that linting with the cache enabled may have different results than running in a deployment pipeline where no cache is available.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Details
What have you changed?
Why are you making these changes?
Both eslint and stylelint support a cache which can be used to only lint files which have changed. This can speed up the linting process which is important when lint tasks are run in pre-commit hooks.
Having an option to clear the cache is also important. Although users could just delete the cache files, doing so via the CLI is easy and acts as a reminder that linting with the cache enabled may have different results than running in a deployment pipeline where no cache is available.