rsnext/docs/api-reference
Alexander Kachkaev 6c8808e90e
Remove outdated & possibly confusing statement about redirects (#33224)
## Documentation / Examples

- [x] Make sure the linting passes by running `yarn lint`

The statement I have removed may be misleading. A colleague of mine has interpreted it as ‘we need to create a custom page or `<Link href="/redirect-path" />` won’t work on the client’. I just ran `npx create-next-app --example redirects redirects-app` and confirmed that this was not necessary.

So saying that redirects “do not affect client-side routing” is probably wrong. They do and they do it the right way.
2022-01-12 17:32:23 +00:00
..
data-fetching Removed backticks on data fetching api titles (#33216) 2022-01-12 14:21:22 +00:00
next Refactor data fetching API docs (#30615) 2022-01-12 08:56:51 +01:00
next.config.js Remove outdated & possibly confusing statement about redirects (#33224) 2022-01-12 17:32:23 +00:00
cli.md feat(cli): introduce next info CLI command (#32972) 2022-01-04 15:35:32 +00:00
create-next-app.md Fixes #33153: Updating cross-references from master to main + canary (#33198) 2022-01-12 02:55:35 +01:00
edge-runtime.md web runtime: add AbortController & AbortSignal (#32089) 2021-12-21 17:12:53 +00:00