feature: Allow user to provide their own content hash to minimise IO operation #129
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.
closing #107
User now can provide an optional argument
--contentHashFilepath
. It is required to be a json format file with the following shape:File path in the file will be relative path from workpsace.
During content hashing phase, if the file is in the map, no IO work will be performed, content hash from the JSON file will be used instead. Otherwise, the existing solution will apply.
N.B. Most of the LOC comes from unit test