Replies: 2 comments 2 replies
-
The docs focus on guides, for the API reference to know what's exported and how it's used, there's a link on the header named API Reference that takes you to https://api.reactrouter.com/v7/ |
Beta Was this translation helpful? Give feedback.
1 reply
-
I'm sorry if this discussion is in the wrong place. Currently if you go to https://github.com/remix-run/react-router/issues and click on "New Issue" and then "🤔 Usage Question (Github Discussions)" you end up creating an issue in the discussion forum for |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The main website mentions that I should be able to upgrade to v7 without any breaking changes and continue to use it. I just recently upgraded from v5 to v6 and in doing so I did EVERY recommended upgrade (with all future flags) which meant using route objects at the top level of my app with
createBrowserRouter
andRouterProvider
.Now however the docs don't seem to mention this stuff at all? The only provided docs talk about either the full Remix+Framework model, or some VERY simple pages about how to use the Component versions. (The only reference in v7 docs I can find is the bare bones API reference).
Was the messaging in the v6 docs accurate? Even if I don't want to switch my SPA app to the full v7 framework, is it still recommended to use
RouterProvider
?Beta Was this translation helpful? Give feedback.
All reactions