You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When reading a resource using .with the resource will load on the initial page load, but navigating between different pages that might use the same resource results in the components getting stuck in the fallback.
Thanks! The new Resource::with() has turned out to be the bane of my existence this week, because it behaves quite differently from the old Resource::with() (now named Resource::map()) or from ::get()... namely that it always returns U instead of Some(U), so whether it returns Some or not doesn't indicate whether it's actually loaded or not!
Linked PR fixes this one without breaking either of the other two cases, so I think it should be... getting better slowly?
Describe the bug
When reading a resource using .with the resource will load on the initial page load, but navigating between different pages that might use the same resource results in the components getting stuck in the fallback.
Leptos Dependencies
Currently on 2b59ae18
To Reproduce
minimal reproduction
Steps to reproduce the behavior:
Expected behavior
Suspense can resolve even if resource is loaded
Additional context
This occurs with
create_local_resource
orcreate_resource
The text was updated successfully, but these errors were encountered: