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.
Following up on this suggestion before looking into using the command for the Gutenberg work I'm doing at the moment.
WIP / RFC
I removed the
CACHE_KEY
computation logic if the parameter was not passed because it was never used. What do you think? I don't think this change would require a major version bump because:So, while technically making
$2
required when it previously wasn't should count as a breaking change, in practice$2
was always required and I think we shouldn't worry with that.However... Since we are taking the time to add options it might be beneficial to use them for both the path to archive and the key to use. That's would make the command more robust, as it would be order agnostic.
save_cache --path PATH_TO_CACHE --key KEY
works just as well assave_cache --key KEY --path PATH_TO_CACHE
butsave_cache PATH_TO_CACHE KEY
andsave_cache KEY PATH_TO_CACHE
produce different results. If we were to do that, then it would definitely count as a breaking change.What do you think?
CHANGELOG.md
if necessary.