rsnext/test/e2e/children-page/index.test.ts
Zack Tanner e02397d264
fix: pages not visible in dev when named children (#54007)
`getEntryKey` had some logic to remove `children` if it was part of the entry (originally it was intended to fix an issue with parallel slots that were used in place of a page, but wasn't working as intended). However, this breaks pages that are named `children`.

Updating this again to implement what I think was the intended behavior in 4900fa21b0 which is to point to the correct entry when a parallel slot is used in place of a page component. 

- x-ref: #52362

Closes NEXT-1514
Fixes #53072
2023-08-15 03:50:37 +00:00

41 lines
1.1 KiB
TypeScript

import { createNextDescribe } from 'e2e-utils'
createNextDescribe(
'children-page',
{
files: __dirname,
},
({ next }) => {
describe('with app dir', () => {
it('should show the content if you have a page named children', async () => {
const browser = await next.browser('/children')
const text = await browser.waitForElementByCss('#children-page').text()
expect(text).toBe('children - app')
const currentDisplay = await browser.eval(
`window.getComputedStyle(document.querySelector('body')).display`
)
expect(currentDisplay).toBe('block')
})
})
describe('with pages dir', () => {
it('should show the content if you have a page named children', async () => {
const browser = await next.browser('/other/children')
const text = await browser.waitForElementByCss('#children-page').text()
expect(text).toBe('children - pages')
const currentDisplay = await browser.eval(
`window.getComputedStyle(document.querySelector('body')).display`
)
expect(currentDisplay).toBe('block')
})
})
}
)