Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change FAQ for dynamic routing #8439

Merged
merged 1 commit into from
Aug 20, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions packages/next/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,7 @@
- [Custom server and routing](#custom-server-and-routing)
- [Disabling file-system routing](#disabling-file-system-routing)
- [Dynamic assetPrefix](#dynamic-assetprefix)
- [Changing x-powered-by](#changing-x-powered-by)
- [Dynamic Import](#dynamic-import)
- [Basic Usage (Also does SSR)](#basic-usage-also-does-ssr)
- [With named exports](#with-named-exports)
Expand Down Expand Up @@ -2739,9 +2740,9 @@ As a result, we were able to introduce a very simple approach to routing that co
<details>
<summary>How do I define a custom fancy route?</summary>

We [added](#custom-server-and-routing) the ability to map between an arbitrary URL and any component by supplying a request handler.
Next.js provide [dynamic routing](#dynamic-routing) solution out of the box. This allows to use pretty links in url.

On the client side, we have a parameter call `as` on `<Link>` that _decorates_ the URL differently from the URL it _fetches_.
You can check an [exmaple](https://github.com/zeit/next.js/tree/canary/examples/dynamic-routing) how it works.

</details>

Expand Down