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

docs(middleware): fix incorrect link to Pages in Middleware's NextResponse section #72223

Merged
merged 2 commits into from
Nov 6, 2024

Conversation

arfa123
Copy link
Contributor

@arfa123 arfa123 commented Nov 2, 2024

This PR fixes an issue in the Middleware documentation where the NextResponse section incorrectly links to Layouts and Templates instead of the intended Pages link.

image

- Replaced the incorrect link to 'layouts-and-templates' with the correct link to 'pages' in the Matcher section of the Middleware documentation. The sentence mentions 'Pages' but the link was incorrect.
@ijjk ijjk added the Documentation Related to Next.js' official documentation. label Nov 2, 2024
@ijjk
Copy link
Member

ijjk commented Nov 2, 2024

Allow CI Workflow Run

  • approve CI run for commit: 93303b6

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Copy link
Contributor

@delbaoliveira delbaoliveira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @arfa123 🙏🏼

@delbaoliveira delbaoliveira merged commit d399ed6 into vercel:canary Nov 6, 2024
39 checks passed
stipsan pushed a commit to sanity-io/next.js that referenced this pull request Nov 6, 2024
…xtResponse` section (vercel#72223)

This PR fixes an issue in the
[Middleware](https://nextjs.org/docs/canary/app/building-your-application/routing/middleware)
documentation where the
[NextResponse](https://nextjs.org/docs/canary/app/building-your-application/routing/middleware#nextresponse)
section incorrectly links to [Layouts and
Templates](https://nextjs.org/docs/canary/app/building-your-application/routing/layouts-and-templates)
instead of the intended
[Pages](https://nextjs.org/docs/canary/app/building-your-application/routing/pages)
link.


![image](https://github.com/user-attachments/assets/6738fb2d-1b93-4cfd-a6d4-bdb158407d11)

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
@arfa123 arfa123 deleted the patch-5 branch November 7, 2024 05:27
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Documentation Related to Next.js' official documentation. locked
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants