Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 45bc628

Browse files
souzasmatheusiansu
authored andcommitted
Fix Markdown comment in proxying docs (#6009)
1 parent 3d1c0ea commit 45bc628

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

‎docusaurus/docs/proxying-api-requests-in-development.md‎

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,9 @@ sidebar_label: Proxying in Development
99
People often serve the front-end React app from the same host and port as their backend implementation.<br>
1010
For example, a production setup might look like this after the app is deployed:
1111

12-
```
13-
/ - static server returns index.html with React app
14-
/todos - static server returns index.html with React app
15-
/api/todos - server handles any /api/* requests using the backend implementation
16-
```
12+
/ - static server returns index.html with React app
13+
/todos - static server returns index.html with React app
14+
/api/todos - server handles any /api/* requests using the backend implementation
1715

1816
Such setup is **not** required. However, if you **do** have a setup like this, it is convenient to write requests like `fetch('/api/todos')` without worrying about redirecting them to another host or port during development.
1917

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /