Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apollo-server-cache-redis: follow-up to #5034 #5088

Merged
merged 1 commit into from Apr 6, 2021

Conversation

glasser
Copy link
Member

@glasser glasser commented Apr 6, 2021

Add docs and changelog. As part of doing this, realize that the implementation
in #5034 makes it annoying to inject a cluster client, so switch the new API to
decide about get vs mget based on which kind of client is passed to the base
class.

Add docs and changelog. As part of doing this, realize that the implementation
in #5034 makes it annoying to inject a cluster client, so switch the new API to
decide about get vs mget based on which kind of client is passed to the base
class.
@glasser glasser force-pushed the glasser/redis-inject-followup branch from 814b643 to b3a829b Compare April 6, 2021 21:41
@glasser glasser enabled auto-merge (squash) April 6, 2021 21:42
@glasser glasser merged commit df06a7c into main Apr 6, 2021
@glasser glasser deleted the glasser/redis-inject-followup branch April 6, 2021 21:47
@glasser
Copy link
Member Author

glasser commented Apr 9, 2021

I've released a prerelease with this fix (apollo-server-cache-redis@1.4.0-alpha.0, part of the Apollo Server 2.23.0 release). Try out the alpha and see if it works for you! Please provide any feedback in #5094.

@glasser
Copy link
Member Author

glasser commented Apr 14, 2021

This has been released in apollo-server-cache-redis@1.4.0.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant