We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I noticed that my cookieConfig settings weren't taking effect on the client, whether it was changing the persist key or the cookie expiration.
The root cause seems to be that the cookieConfigs are only being used on the server.
next-redux-cookie-wrapper/src/index.tsx
Lines 126 to 132 in e2616e3
Whereas on the client, no cookieConfig is being used:
Line 164 in e2616e3
Line 71 in e2616e3
The text was updated successfully, but these errors were encountered:
37d625e
chore(Release): 1.1.2 [skip ci]
611b5e7
### [1.1.2](v1.1.1...v1.1.2) (2020-07-14) ### Bug Fixes * Pass `cookieConfig` to `CookieStorage` on client side ([37d625e](37d625e)), closes [#7](#7)
🎉 This issue has been resolved in version 1.1.2 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
Wow, the bot was faster than me 😄 Anyway, thanks for pointing this out!
Thanks for the quick fix!
No branches or pull requests
I noticed that my cookieConfig settings weren't taking effect on the client, whether it was changing the persist key or the cookie expiration.
The root cause seems to be that the cookieConfigs are only being used on the server.
next-redux-cookie-wrapper/src/index.tsx
Lines 126 to 132 in e2616e3
Whereas on the client, no cookieConfig is being used:
next-redux-cookie-wrapper/src/index.tsx
Line 164 in e2616e3
next-redux-cookie-wrapper/src/index.tsx
Line 71 in e2616e3
The text was updated successfully, but these errors were encountered: