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

test(nextjs): Fix canary tests #12875

Merged
merged 1 commit into from
Jul 11, 2024
Merged

test(nextjs): Fix canary tests #12875

merged 1 commit into from
Jul 11, 2024

Conversation

lforst
Copy link
Member

@lforst lforst commented Jul 11, 2024

@lforst lforst requested a review from chargome July 11, 2024 11:36
@@ -39,7 +39,10 @@ test('Creates a navigation transaction for app router routes', async ({ page })

const serverComponentTransactionPromise = waitForTransaction('nextjs-app-dir', async transactionEvent => {
return (
transactionEvent?.transaction === 'GET /server-component/parameter/foo/bar/baz' &&
// It seems to differ between Next.js versions whether the route is parameterized or not
Copy link
Member

Choose a reason for hiding this comment

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

This seems bad and something we should fix. Doesn't this mean paramaterization breaks in the newest nextjs version?

Copy link
Member Author

@lforst lforst Jul 11, 2024

Choose a reason for hiding this comment

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

It's the newer versions that have the parameterized routes. Me and Francesco agreed that relay parameterization is good enough that we can just delegate the parameterization to Next.js. If it breaks, it breaks.

All of that shouldn't block this PR though.

@lforst lforst merged commit 963eab7 into develop Jul 11, 2024
100 checks passed
@lforst lforst deleted the lforst-fix-cnry-nextjs branch July 11, 2024 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants