-
Notifications
You must be signed in to change notification settings - Fork 118
feat: add cookie attributes #301
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
base: main
Are you sure you want to change the base?
Conversation
β Deploy Preview for nuxt-color-mode canceled.
|
|
May i ask to improve naming? Would be nice to use |
tasiotas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cookieAttribs renamed to cookieAttrs
|
I'm wondering, I don't think domain is very useful though, but what about just forcing the path to be |
|
any updates? |
|
lgtm, tried locally with the cookieAttrs changes and that pesky "Some cookies are misusing the recommended βSameSiteβ attribute" is gone |
Saving the current `color mode` in a cookie to avoid `hydration issues`, as this way the `server` already knows the current `color mode`. It was necessary to use `useCookie()` to save the `color mode` instead of the `storage setting` of `nuxtjs/color-mode`, as the cookie value otherwise will be applied to the current `/path`. Resulting in different `color modes` for different `paths. See: nuxt-modules/color-mode#301
Saving the current `color mode` in a cookie to avoid `hydration issues`, as this way the `server` already knows the current `color mode`. It was necessary to use `useCookie()` to save the `color mode` instead of the `storage setting` of `nuxtjs/color-mode`, as the cookie value otherwise will be applied to the current `/path`. Resulting in different `color modes` for different `paths. See: nuxt-modules/color-mode#301
Saving the current `color mode` in a cookie to avoid `hydration issues`, as this way the `server` already knows the current `color mode`. It was necessary to use `useCookie()` to save the `color mode` instead of the `storage setting` of `nuxtjs/color-mode`, as the cookie value otherwise will be applied to the current `/path`. Resulting in different `color modes` for different `paths. See: nuxt-modules/color-mode#301
Saving the current `color mode` in a cookie to avoid `hydration issues`, as this way the `server` already knows the current `color mode`. It was necessary to use `useCookie()` to save the `color mode` instead of the `storage setting` of `nuxtjs/color-mode`, as the cookie value otherwise will be applied to the current `/path`. Resulting in different `color modes` for different `paths. See: nuxt-modules/color-mode#301
Saving the current `color mode` in a cookie to avoid `hydration issues`, as this way the `server` already knows the current `color mode`. It was necessary to use `useCookie()` to save the `color mode` instead of the `storage setting` of `nuxtjs/color-mode`, as the cookie value otherwise will be applied to the current `/path`. Resulting in different `color modes` for different `paths. See: nuxt-modules/color-mode#301
|
partial support landed via #320, but we can iterate here to allow configuration |
π Linked issue
none
β Type of change
π Description
I added
cookieAttribsto the module config. This allows to specify any cookie attribute for further configuration. Now we can specifypath,domainetc. so that color-mode works across subdomains.Thank you