fix(useMediaQuery): On misconfiguration, cause hydration error instea… #1042
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.
What is the current behavior, and the steps to reproduce the issue?
When the hook is misconfigured, that is, when
initializeWithValue
istrue
during SSR, the hooks crashes instead of producing a hydration error, which is not in line with the behavior of the rest of the isomorphic hooks.What is the expected behavior?
Hydration error instead of a crash.
How does this PR fix the problem?
If the rendering environment is not a browser, set
initializeWithValue
tofalse
.This solution makes me wonder: what is the purpose of the
initializeWithValue
option anymore? If it is set tofalse
during SSR anyway, why have it at all? Is there a usecase for having the hook returnundefined
on first render when doing client-side rendering?Checklist
useMediaQuery
has the "correct" initial value #1000