feat: add an optional cache that speeds up consecutive runs #38
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.
used like:
In our project with 1100 scanned files, cached runs go down from 2 seconds to 0.3 seconds. And the terminal is less spamy as it only reports changed files.
The cache is implemented as careful as possible:
--cache-file
option)But even if you don't use the cache, uncached is faster as well, as the
.union
calls that I removed shaved off half a second as well for us.A cached run looks like this: