This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-27
Channels
- # babashka (45)
- # beginners (44)
- # calva (3)
- # cider (14)
- # clara (4)
- # clj-commons (3)
- # clj-otel (4)
- # cljsjs (1)
- # cljsrn (111)
- # clojars (5)
- # clojure (62)
- # clojure-europe (14)
- # clojure-nl (2)
- # clojure-uk (4)
- # clojurescript (31)
- # community-development (16)
- # conjure (7)
- # cursive (9)
- # data-science (1)
- # datalevin (10)
- # docker (1)
- # emacs (20)
- # fulcro (7)
- # helix (10)
- # jobs (4)
- # lsp (22)
- # malli (35)
- # meander (12)
- # music (1)
- # nbb (2)
- # off-topic (5)
- # pathom (3)
- # quil (1)
- # re-frame (12)
- # react (6)
- # reagent (18)
- # releases (1)
- # remote-jobs (1)
- # rewrite-clj (4)
- # ring (1)
- # shadow-cljs (10)
- # spacemacs (9)
- # tools-build (17)
yeah I'm thinking about how we could migrate to react-router, if at all. I think the model seems good
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
^ above is only in regards to the router, as Remix itself does have great ideas and they’re great a explaining them!
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
I was looking at useFetcher. It works for json. I didn't enconter a way to process the return myself. Have you tried useFetcher ?
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.
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