Release 3.10.0 #6662
Release 3.10.0 #6662
Conversation
…for custom cache keys (#6655) Create a new hook (`generateCacheKey`) on the `ApolloServerPluginResponseCache` constructor options which allows users to customize the cache key used by returning their own `string`. The hook receives two arguments: the `requestContext` and an object (`cacheKeyData`) which contains the following properties: `source` `operationName` `variables` `extra` (computed by `options.extraCacheKeyData`) `sessionId` `sessionMode`
|
✅ Deploy Preview for apollo-server-docs canceled.
|
|
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 7d6d3ce:
|
|
Note: #6628 landed to |
|
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 4041aae:
|
- Rename BaseCacheKey and ContextualCacheKey with "Data" on end, since the cache key is a string. - Reintroduce CacheKey(Data) removed in #6655; make the GenerateCacheKeyFunction type be defined in terms of it. Now calls to the `const generateCacheKey` function are type-safe (ie, the second arg is a CacheKeyData rather than unknown). - Describe generateCacheKey hook as a method rather than a field, like the other hooks in Options.
- apollo-reporting-protobuf@3.3.2 - apollo-server-azure-functions@3.10.0 - apollo-server-cloud-functions@3.10.0 - apollo-server-cloudflare@3.10.0 - apollo-server-core@3.10.0 - apollo-server-express@3.10.0 - apollo-server-fastify@3.10.0 - apollo-server-hapi@3.10.0 - apollo-server-integration-testsuite@3.10.0 - apollo-server-koa@3.10.0 - apollo-server-lambda@3.10.0 - apollo-server-micro@3.10.0 - apollo-server-plugin-base@3.6.2 - apollo-server-plugin-response-cache@3.7.0 - apollo-server-types@3.6.2 - apollo-server@3.10.0
As with release PRs in the past, this is a PR tracking a
release-x.y.zbranch for an upcoming release of Apollo Server. 🙌 The version in the title of this PR should correspond to the appropriate branch.Check the appropriate milestone (to the right) for more details on what we hope to get into this release!
The intention of these release branches is to gather changes which are intended to land in a specific version (again, indicated by the subject of this PR). Release branches allow additional clarity into what is being staged, provide a forum for comments from the community pertaining to the release's stability, and to facilitate the creation of pre-releases (e.g.
alpha,beta,rc) without affecting themainbranch.PRs for new features might be opened against or re-targeted to this branch by the project maintainers. The
mainbranch may be periodically merged into this branch up until the point in time that this branch is being prepared for release. Depending on the size of the release, this may be once it reaches RC (release candidate) stage with an-rc.xrelease suffix. Some less substantial releases may be short-lived and may never have pre-release versions.When this version is officially released onto the
latestnpm tag, this PR will be merged intomain.