react

2022-06-27T11:23:07.018459Z

I was looking at useFetcher. It works for json. I didn't enconter a way to process the return myself. Have you tried useFetcher ?

2022-06-27T14:40:58.039659Z

I misunderstood the useFetcher mechanism. fetcher.load(href) is called on route. And triggers the loader function. So no problem with toJson being called . My mistake.

lilactown 2022-06-27T04:21:30.403159Z

yeah I'm thinking about how we could migrate to react-router, if at all. I think the model seems good

lilactown 2022-06-29T13:16:07.759929Z

yeah I know there are lots of changes between react router versions. it does seem like they've eventually landed on a good model, though. and they have funding

Aleed 2022-06-27T15:33:33.420719Z

tbh, it’s been a known issue that the nested routing in react-router leads to waterfall requests that was one of the main criticisms of their v3->v4 changes https://medium.com/@taion/react-routing-and-data-fetching-ec519428135c above video makes it seem like these are novel solutions driven by Remix’s design, rather than problems they’ve neglected despite lots of breaking changes in a few years time

Aleed 2022-06-27T15:36:45.187199Z

^ above is only in regards to the router, as Remix itself does have great ideas and they’re great a explaining them!