-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
chore: app router - /getting-started page #18185
Conversation
Graphite Automations"Add consumer team as reviewer" took an action on this PR • (12/14/24)1 reviewer was added to this PR based on Keith Williams's automation. "Add foundation team as reviewer" took an action on this PR • (12/17/24)1 reviewer was added to this PR based on Keith Williams's automation. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
E2E results are ready! |
@@ -147,11 +146,6 @@ const OnboardingPage = (props: PageProps) => { | |||
)} | |||
data-testid="onboarding" | |||
key={pathname}> | |||
<Head> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Head should be removed in app router. It's replaced by generateMetadata
in app router route.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's working well 👍🏼 And I love how you split these into smaller PRs.
* remove env vars * move pages to /app * remove Head component * remove pages router * add to config matcher * fix
What does this PR do?
Test (email-signup onboarding flow)
Screen.Recording.2024-12-17.at.11.58.25.PM.mov
Mandatory Tasks (DO NOT REMOVE)
How should this be tested?