Consolidate Router component

Author: albertogasparin

docs/_sidebar.md

@@ -11,7 +11,6 @@
 * **Router**
 
   - [Configuration](/router/configuration.md)
-  - [Selection](/router/selection.md)
   - [State](/router/state.md)
   - [SSR](/router/ssr.md)
 

docs/api/components.md

@@ -29,82 +29,34 @@ import { appRoutes } from './routing';
 
 ### Router props
 
-| prop              | type                      | description                                                                                        |
-| ----------------- | ------------------------- | -------------------------------------------------------------------------------------------------- |
-| `routes`          | `Routes[]`                | Your application's routes                                                                          |
-| `initialRoute`    | `Route`                   | The route your application is initially showing                                                    |
-| `history`         | `History`                 | The history instance for the router                                                                |
-| `basePath`        | `string`                  | Base path string that will get prepended to all route paths                                        |
-| `resourceContext` | `ResourceContext`         | Custom contextual data that will be provided to all your resources' `getKey` and `getData` methods |
-| `resourceData`    | `ResourceData`            | Pre-resolved resource data. When provided, the router will not request resources on mount          |
-| `onPrefetch`      | `function(RouterContext)` | Called when prefetch is triggered from a Link                                                      |
-
-## StaticRouter
-
-If you are planning to render your application on the server, you must use the `StaticRouter` in your server side entry. The `StaticRouter` should only be used on server as it omits all browser-only resources. It does not require a `history` prop to be provided, instead, you simply need to provide the current `location` as a string. In order to achieve this, we recommend your server side application uses [`jsdom`](https://github.com/jsdom/jsdom).
-
-```js
-// server-app.js
-import { StaticRouter } from 'react-resource-router';
-import { App } from '../components';
-import { appRoutes } from '../routing';
-
-const { pathname, search } = window.location;
-const location = `${pathname}${search}`;
-
-export const ServerApp = () => (
-  <StaticRouter routes={appRoutes} location={location}>
-    <App />
-  </StaticRouter>
-);
-```
-
-### StaticRouter props
-
-| prop       | type       | description                                                 |
-| ---------- | ---------- | ----------------------------------------------------------- |
-| `routes`   | `Routes[]` | Your application's routes                                   |
-| `location` | `string`   | The string representation of the app's current location     |
-| `basePath` | `string`   | Base path string that will get prepended to all route paths |
+| prop              | type                      | description                                                                                                                                   |
+| ----------------- | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `routes`          | `Routes[]`                | Your application's routes                                                                                                                     |
+| `history`         | `History`                 | The history instance for the router, if omitted memory history will be used (optional but recommended)                                        |
+| `location`        | `string`                  | If `history` prop is omitted, this configures the initial location for the default memory history (optional, useful for tests and storybooks) |
+| `basePath`        | `string`                  | Base path string that will get prepended to all route paths (optional)                                                                        |
+| `initialRoute`    | `Route`                   | The route your application is initially showing, it's a performance optimisation to avoid route matching cost on initial render(optional)     |
+| `resourceContext` | `ResourceContext`         | Custom contextual data that will be provided to all your resources' `getKey` and `getData` methods (optional)                                 |
+| `resourceData`    | `ResourceData`            | Pre-resolved resource data. When provided, the router will not request resources on mount (optional)                                          |
+| `onPrefetch`      | `function(RouterContext)` | Called when prefetch is triggered from a Link (optional)                                                                                      |
 
 ## MemoryRouter
 
 The `MemoryRouter` component can be used for your application's unit tests.
 
 ```js
 it('should send right props after render with routes', () => {
-  mount(
-    <MemoryRouter routes={[mockRoutes[0]]}>
-      <RouterSubscriber>
-        {({ history, location, routes, route, match, query }) => {
-          expect(history).toEqual(mockHistory);
-          expect(location).toEqual(mockLocation);
-          expect(routes).toEqual(routes);
-          expect(route).toEqual(
-            expect.objectContaining({
-              path: `/pathname`,
-            })
-          );
-          expect(match).toBeTruthy();
-          expect(query).toEqual({
-            foo: 'bar',
-          });
-
-          return <div>I am a subscriber</div>;
-        }}
-      </RouterSubscriber>
-    </MemoryRouter>
-  );
+  render(<MemoryRouter routes={[mockRoutes[0]]}>{/* ... */}</MemoryRouter>);
 });
 ```
 
 ### MemoryRouter props
 
 | prop       | type       | description                                                 |
 | ---------- | ---------- | ----------------------------------------------------------- |
-| `routes`   | `Routes[]` | Your application's routes                                   |
-| `location` | `string`   | The string representation of the app's current location     |
 | `basePath` | `string`   | Base path string that will get prepended to all route paths |
+| `location` | `string`   | The string representation of the app's current location     |
+| `routes`   | `Routes[]` | Your application's routes                                   |
 
 ## Link component
 

docs/router/README.md

@@ -1,6 +1,5 @@
 - **Router**
 
   - [Configuration](./configuration.md)
-  - [Selection](./selection.md)
   - [State](./state.md)
   - [SSR](./ssr.md)

docs/router/selection.md

@@ -22,22 +22,25 @@ import { RouteComponent } from 'react-resource-router';
 
 export const App = () => (
   <>
+    <Navigation />
     <RouteComponent />
+    <Footer />
   </>
 );
 ```
 
-The reason for this is that currently, you will need to use the [`Router`](#router-component) component on the client and the [`StaticRouter`](#staticrouter-component) component on the server. Following the above composition pattern will allow you to use the correct router in your server side entry and client side entry respectively. This could look something like the following examples:
+When however you need to SSR your app, we need pass different props to Router, as `createBrowserHistory` does not really work on server, so we recommend to use `location` instead (or pass your own `MemoryHistory` if needed)
 
 ```js
 // server-app.js
-import { StaticRouter } from 'react-resource-router';
+import { Router } from 'react-resource-router';
 import { App } from '../components';
+import { routes } from '../routing/routes';
 
-export const ServerApp = ({ location, routes }) => (
-  <StaticRouter routes={routes} location={location}>
+export const ServerApp = ({ location }) => (
+  <Router routes={routes} location={location}>
     <App />
-  </StaticRouter>
+  </Router>
 );
 ```
 
@@ -60,21 +63,21 @@ export const ClientApp = () => (
 
 Until React Suspense works on the server, we cannot do progressive rendering server side. To get around this, we need to `await` all resource requests to render our app _with all our resource data_ on the server.
 
-Luckily the `StaticRouter` provides a convenient static method to do this for us.
+Luckily the `Router` provides a convenient static method to do this for us.
 
 ```js
 import { renderToString } from 'react-dom/server';
-import { StaticRouter } from 'react-resource-router';
+import { Router } from 'react-resource-router';
 import { routes } from '../routing/routes';
 import { ServerApp } from './app';
 
 const renderToStringWithData = async ({ location }) => {
-  await StaticRouter.requestResources({ location, routes });
+  await Router.requestResources({ location, routes });
 
-  return renderToString(<ServerApp routes={routes} location={location} />);
+  return renderToString(<ServerApp location={location} />);
 };
 ```
 
-Notice that we do not need to provide any `resourceData` object to the `ServerApp`, the `StaticRouter` handles this for us internally.
+Notice that we do not need to provide any `resourceData` object to the `ServerApp`, the `Router` handles this for us internally.
 
-To prevent slow APIs from causing long renders on the server you can optionally pass in `timeout` as an option to `StaticRouter.requestResources`. If a route resource does not return within the specified time then its data and promise will be set to null.
+To prevent slow APIs from causing long renders on the server you can optionally pass in `timeout` as an option to `Router.requestResources`. If a route resource does not return within the specified time then its data and promise will be set to null.

docs/router/ssr.md

@@ -0,0 +1,10 @@
+import React from 'react';
+
+import { Link } from 'react-resource-router';
+
+export const About = () => (
+  <div>
+    <h1>About</h1>
+    <Link to="/">Go to home</Link>
+  </div>
+);

examples/hash-routing/about.tsx

@@ -0,0 +1,10 @@
+import React from 'react';
+
+import { Link } from 'react-resource-router';
+
+export const Home = () => (
+  <div>
+    <h1>Home</h1>
+    <Link to="/about">Go to about</Link>
+  </div>
+);

examples/hash-routing/home.tsx

@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <title>Example - Hash Routing</title>
+  </head>
+
+  <body>
+    <div id="root"></div>
+    <script src="bundle.js" type="text/javascript"></script>
+  </body>
+</html>

examples/hash-routing/index.html

@@ -0,0 +1,45 @@
+import { createHashHistory as createHashHistory4 } from 'history';
+import { createHashHistory as createHashHistory5 } from 'history-5';
+import React from 'react';
+import { render } from 'react-dom';
+
+import { About } from './about';
+import { Home } from './home';
+
+import { Redirect, RouteComponent, Router } from 'react-resource-router';
+
+// eslint-disable-next-line @typescript-eslint/no-unused-vars
+const history4 = createHashHistory4();
+const history5 = createHashHistory5();
+const history = history5;
+
+const routes = [
+  {
+    name: 'home',
+    path: '/home',
+    exact: true,
+    component: () => <Home />,
+  },
+  {
+    name: 'about',
+    path: '/about',
+    exact: true,
+    component: () => <About />,
+  },
+  {
+    name: 'default',
+    path: '/*',
+    exact: true,
+    component: () => <Redirect to="/home" />,
+  },
+];
+
+const App = () => {
+  return (
+    <Router history={history} routes={routes}>
+      <RouteComponent />
+    </Router>
+  );
+};
+
+render(<App />, document.getElementById('root'));

examples/hash-routing/index.tsx

@@ -3,7 +3,6 @@ import { render } from 'react-dom';
 
 import Home from './home';
 import PathParamExample from './use-path-param';
-import QueryParamExample from './use-query-param';
 
 import {
   Router,
@@ -12,6 +11,8 @@ import {
   createRouterSelector,
 } from 'react-resource-router';
 
+import QueryParamExample from './use-query-param';
+
 const myHistory = createBrowserHistory();
 const useRouteName = createRouterSelector(s => s.route.name);