Open njust opened 1 month ago
In part, this is a (known but hard to fix) bug with nested Suspense and resources.
In part, this is an anti-pattern you should avoid if it is at all possible. Specifically, you should hoist all data-loading as high as possible in the application. Loading data in the way you're doing it creates a waterfall and prevents anything from running concurrently -- each component needs to wait for the previous component to finish loading before it even begins loading.
Describe the bug A recursive component like this:
Fails to hydrate with an error:
Leptos Dependencies
To Reproduce A minimal example which reproduces this issue can be found here: https://github.com/njust/leptos_hydration_issue
Expected behavior No error during hydration