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.

Sign up for GitHub

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

Jump to bottom

Creating app/page/page.tsx maps to app/page.tsx #42010

Closed
balazsorban44 opened this issue Oct 27, 2022 · 1 comment · Fixed by #42348
Closed

Creating app/page/page.tsx maps to app/page.tsx #42010

balazsorban44 opened this issue Oct 27, 2022 · 1 comment · Fixed by #42348
Assignees
@shuding
Labels
area: app App directory (appDir: true)

Comments

@balazsorban44
Copy link
Member

balazsorban44 commented Oct 27, 2022 •
edited
Loading 

  Creating a page at route `/page` by making a file at `app/page/page.tsx` gets mapped to `app/page.tsx`, so basically `/page` route renders the same content as the `/` route. This doesn't seem to be the expected behavior.

Originally posted by @bhavesh-chaudhari in #41745 (comment)

Reproduction repository: https://github.com/balazsorban44/42010
@balazsorban44 balazsorban44 changed the title Creating a page at route /page by making a file at app/page/page.tsx gets mapped to app/page.tsx, so basically /page route renders the same content as the / route. This doesn't seem to be the expected behavior. Creating app/page/page.tsx maps to app/page.tsx Oct 27, 2022
@balazsorban44 balazsorban44 added kind: bug area: app App directory (appDir: true) labels Oct 27, 2022
@shuding shuding mentioned this issue Nov 2, 2022
Merged
11 tasks
shuding added a commit that referenced this issue Nov 2, 2022
@shuding
Fix page folder being wrongly resolved as page file (#42348)
b69dac1 
Closes #42010.

## Bug

- [ ] Related issues linked using `fixes #number`
- [x] Integration tests added
- [ ] Errors have a 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 a helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `pnpm build && pnpm lint`
- [ ] The "examples guidelines" are followed from [our contributing
doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2022

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@shuding shuding

Labels
area: app App directory (appDir: true)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix page folder being wrongly resolved as page file vercel/next.js
3 participants
@shuding @huozhi @balazsorban44