Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2022-06-27

Channels

#react
<
2022-06-27
>
lilactown04:06:30

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

Aleed15:06:33

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

Aleed15:06:45

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

lilactown13:06:07

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

geraldodev11:06:07

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

geraldodev14:06:58

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.

Aleed15:06:33

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