Router Loaders parallelism in a CRM app project
Hello,
I am really wondering what should be the best use-cases for loaders in my case. I am building a CRM using tanstack-router and I have a lot of URLs like this:
Any advices? Should I only be using loaders for my top-level entity page and not for nested routes?
Phil
I am really wondering what should be the best use-cases for loaders in my case. I am building a CRM using tanstack-router and I have a lot of URLs like this:
/entity/$entityId/entityBs or /entity/$entityId/entityBs/$entityBId. My problem is what is $entityId does not exists server-side, all the loaders of the child routes still gets executed for no reason since we know the parent does not exist.Any advices? Should I only be using loaders for my top-level entity page and not for nested routes?
Phil
