fix(dark-mode): avoid localStorage overwrite by system dark mode status #636
+85
−15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem Description
While using
useDarkMode
, I noticed that after refreshing the page, the value saved inlocalStorage
does not take effect (observing thatlocalStorage
is always overwritten by the current system's dark mode status), even though I set theinitializeWithValue
option to true (the documentation states, "If true (default), the hook will initialize by readinglocalStorage
").Cause of the Issue
The value saved in
localStorage
does not take effect on the next page load because the value retrieved byconst isDarkOS = useMediaQuery()
immediately overwrites the result read fromuseLocalStorage()
when theuseDarkMode
hook initializes (sinceuseIsomorphicLayoutEffect
executes immediately). This behavior is unexpected, causing the functionality of saving the dark mode state tolocalStorage
to fail.Fix
Add
const allowDarkOSChange = useIsMounted()
. Before the page is mounted, prevent applying the dark mode result fromisDarkOS
, rather than immediately executing and overwriting the value fromlocalStorage
.Test cases have been added to verify the existence of this issue, and the problem was confirmed. The code modification has passed the tests successfully.
fixes #512