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

chore: Update redis package to v4 #932

Merged
merged 1 commit into from
Feb 27, 2023
Merged

chore: Update redis package to v4 #932

merged 1 commit into from
Feb 27, 2023

Conversation

MonkeyDo
Copy link
Member

We use 'legacyMode' in order to play well with the connect-redis package (which links ExpressJS sessions to Redis). This also means we don't need to change the structure of the createClient args object. See tj/connect-redis#337 (comment)

Also of interest, the redis package changelog: https://github.com/redis/node-redis/blob/redis%404.0.0/packages/client/CHANGELOG.md

We use 'legacyMode' in order to play well with the connect-redis package (which links Express sessions to Redis).
This also means we don't need to change the structure of the createClient args object.
See  https://github.com/redis/node-redis/blob/redis%404.0.0/packages/client/CHANGELOG.md
Copy link
Collaborator

@leftmostcat leftmostcat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems sensible, particularly given the constraints.

@MonkeyDo MonkeyDo merged commit b028b8d into master Feb 27, 2023
@MonkeyDo MonkeyDo deleted the update-redis branch February 27, 2023 12:33
@MonkeyDo
Copy link
Member Author

Thanks for the sanity check @leftmostcat !

MonkeyDo added a commit that referenced this pull request Mar 3, 2023
Changed it in the API main entry but not in the website's…
See #932
@MonkeyDo MonkeyDo mentioned this pull request Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants