feat(compute-key): add support for mapKeyToCacheKey

code-forger commented 1 year ago

this option allows consumers to directly vary their cache key

Motivation and Context

This change enables more advanced caching features, where the cached data is not directly tied to a single complete url.

unit tests, run locally in a module. This is a non-breaking change. No existing unit test was changed of fails.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation (adding or updating documentation)
[ ] Dependency update

[x] My change requires a change to the documentation and I have updated the documentation accordingly.
[x] My changes are in sync with the code style of this project.
[x] There aren't any other open Pull Requests for the same issue/update.
[ ] These changes should be applied to a maintenance branch.
[ ] I have added the Apache 2.0 license header to any new files created.

New functionality

codesandbox-ci[bot] commented 1 year ago

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit a693a0755f25f64144b6b44872f5b7e215fccfcd:

Sandbox	Source
quick-install	Configuration
fetchye-provider-install	Configuration
fetchye-redux-provider-install	Configuration
nextjs-fetchye-ssr	Configuration

aneudy1702 commented 1 year ago

@code-forger , thanks this is very promising. how does this work with the SSR request?

namely,

const fetchye = makeOneServerFetchye({ store, fetchClient });

is makeOneServerFetchye able to take this additional parameter to map the cache key?