-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
[Solid Query] Hydration Mismatch error #2132
Comments
This was solved here: https://discord.com/channels/722131463138705510/1229910798135066716/1230151418569298052 |
Yeah, a workaround of The issue seems to be that as soon as Switch matches a case it renders and flushes the data. So in this case when |
it works a bit different with solid-query 5.29:
|
attn @ardeora |
It's pretty hard for me to debug Solid Query stuff. Like I need to put time aside to get into the code base. It might be easiest to report bugs against them and then they make reproductions with pure |
Apologies @ryansolid Here is an example with just using I think the Switch component (during SSR) eagerly evaluates and flushes the data when any case matches? In this case you would always see the |
Sorry took me a while to look at this. But in the If I remove the first condition or change the first switch condition to the following it works. <Match when={!data() && data.loading}>pending</Match> The reason reading loading doesn't suspend is it is the mechanism we use to purposefully opt into tearing. But tearing during hydration won't work. However making that fix in the Solid Query example I think still doesn't work. It doesn't error during hydration but it also doesn't show anything. So we will need to narrow this down further. |
Describe the bug
Getting an error:
Your Example Website or App
https://stackblitz.com/edit/github-pqy8j7-jhayd9?file=src%2Fcomponents%2FPage.tsx
Steps to Reproduce the Bug or Issue
Expected behavior
Blank page is displayed, with no errors in console.
Screenshots or Videos
No response
Platform
Windows, Chrome 123
Additional context
No response
The text was updated successfully, but these errors were encountered: