Love you I understand what you mean but the fact is that those resources do not exist (yet) and may not for some time. Hope this helps whoever comes next with some similar issue. I just feel the clarifying paragraph should be pointed out more strongly, or maybe even stated somewhere more findable (higher on the docs tree?) So, all that said, I also want to show some love for the contributors and commiters, this library is fantastic and I wouldn't have achieved what I needed without it. Seems to me that being this such a tricky way to cope with the history issue, it should be pointed out more strongly. Note that this is not required to use state management libs alongside React Router, it's only for deep integration.Īs I said, the docs are really fine. The most common use-case for using the low-level is to synchronize a custom history with a state management lib like Redux or Mobx.
Just then (and fighting the urge to read only the code blocks) I found:
go back and (finally) check the Router.md file.check on the history.md to find not-too-helpful readme.go back to realize there's an api folder.check guides folder on the repo (which, you know, newbies like me tend to be attracted to).check the docs folder on the react-router repo.find nothing too useful on the main readme (regarding history).follow the link to Router ( react-router).ignore the beautiful link to docs (which leads to another site, so the rest of the docs on github remain ignored).Hence, I believe, the issue is that in order to find this clarifying doc I had to: md (which I failed to find) was quite clarifying (after having found this very issue/comment/thread). The guides are really nice, I just missed the difference between react-router-dom and react-router, but the particular. I just feel that a bigger heads up regarding history should be included. I feel I need to further explain my particular confusion with the docs. The documentation seems to be trying to be minimalist and comes across as though whoever wrote it didn't have much consideration for anyone starting out with this.Īll and all, this is just extremely hard for any beginner/intermediate to understand or attempt to implement - quite aside from the fact that it's so different to the previous implementations. I've so far spent the past month in my spare time trying to understand v4 router and it feels ridiculously hard if not impossible to get my head around. Everything is written at a level that seems to assume that you already understand everything that it's telling you - that's not very beginner friendly.Some examples don't make sense, they have classes with just jsx beneath it or objects that aren't clear what they are for or how they are received/obtained.
All examples are all written as though it's a single file in context when in real world cases you're not in a single file.It feels like almost no examples show what's been imported/exported.IMO the problem with the documentation is that none of it is clear to understand or use