3bd42b4d0b
In order to turn the API Routes docs more clear about the file extensions when using `pageExtensions`. I know that it was already explained [here](https://nextjs.org/docs/api-reference/next.config.js/custom-page-extensions). But just think about the DX: If a developer have a trouble with an API endpoint not working properly should it check it on custom-page-extensions page or api-routes page itself?? Related to https://github.com/vercel/next.js/issues/8178. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint` Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| api-middlewares.md | ||
| dynamic-api-routes.md | ||
| introduction.md | ||
| response-helpers.md | ||