fix: cache key seed must increment regardless of config of host project #15
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.
We had a short incident because 1.2.0 changed the default cache key seed, but I didn't think to change my app's configured cache key seed.
I also brought in the fix for issue #14 because I needed cache assertions any way.
Improved unit test coverage about the shape of the cached data, and discovered we didn't really test cache read and cache write independently so beefed that up, too.