Post

I'm actually considering writing a series of blog posts called "React Router Mental Models" to try to explain some of the parts of the current docs that I feel don't give enough context. Mostly coz I'm tired of answering the same questions over and over again in the Discord 😅

some items on my list.. - when loaders are called, when "revalidation" happens - loaders<->sessionStorage, or generally how to work with state when it's not in the URL - pairing with something like AGGrid server-side row model - non-trivial testing examples, when to rely on msw vs createRoutesStub

That's basically why I wrote my "Guide to React Rendering Behavior" post :) It's primarily external visible behavior rather than impl details, but it definitely tries to address that mental model due to consistent misunderstandings I see in the wild: blog.isquaredsoftware.com/2020/05/blog...

If you repeated something more than twice you'd start questioning your career choice.

Too much documentation claims some sort of handy wavy magic when it’s really an abstraction over one or more web apis. YMMV but I find understanding what the abstraction does to be a helpful mental model for using that tool

I think the problem with discussing implementation details in documentation is that you risk people relying on those implementation details in weird ways. I’d still like to see more of it, but I also understand there’s a trade off.

Like a “this may seem a bit weird, but here’s why we did it” would be cool in a lot of places

Consumers relying on implementation details is part of why I liked to keep them hidden. I don’t think it’s worth the trade off though. Knowing implementation details gives you more confidence to build on top, lets you better understand what’s possible, and gives you more context when debugging.