Skip to content

Commit eb3baa7

Browse files
committed
Whitespace & caps
1 parent 194b157 commit eb3baa7

File tree

1 file changed

+3
-12
lines changed

1 file changed

+3
-12
lines changed

doc/00 Guides/ServerRendering.md

Lines changed: 3 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -60,17 +60,8 @@ function renderFullPage(html, initialData) {
6060

6161
### API Routes
6262

63-
Sometimes servers function as both the UI server and the api server. Do
64-
your best to think of them separately.
63+
Sometimes servers function as both the UI server and the API server. Do your best to think of them separately.
6564

66-
While historically we've allowed one URL to function as both an API and
67-
a UI server that branches behavior on the "accepts" header, you're
68-
better off just having separate routes. Might I suggest you namespace
69-
your api routes with `/api/...`?
65+
While historically we've allowed one URL to function as both an API and a UI server that branches behavior on the "accepts" header, you're better off just having separate routes. Might I suggest you namespace your API routes with `/api/...`?
7066

71-
You could certainly add methods to your React Router routes to handle
72-
API requests, match the routes, inspect the accepts header, then call
73-
the methods on your route instead of rendering the components. I was
74-
about to tell you not to do this, but please do and let us know how it
75-
goes. Most of us should probably just use the server side router from
76-
our favorite libraries for now, though.
67+
You could certainly add methods to your React Router routes to handle API requests, match the routes, inspect the accepts header, then call the methods on your route instead of rendering the components. I was about to tell you not to do this, but please do and let us know how it goes. Most of us should probably just use the server side router from our favorite libraries for now, though.

0 commit comments

Comments
 (0)