-
Notifications
You must be signed in to change notification settings - Fork 3
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
Migrate doi pages to app router #342
Conversation
Passing run #1075 ↗︎
Details:
Review all test suite changes for PR #342 ↗︎ |
3 flaky tests on run #1051 ↗︎
Details:
search.test.ts • 1 flaky test • Tests
personContainer.test.ts • 1 flaky test • Tests
statistics.test.ts • 1 flaky test • Tests
Review all test suite changes for PR #342 ↗︎ |
src/app/doi.org/[...doi]/page.tsx
Outdated
if (!data) return notFound() | ||
|
||
|
||
// return <script type="application/ld+json">{work.schemaOrg}</script> |
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.
This seems out of place here
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.
This originates from here. The app router doesn't like having scripts in the <Head>
like we had in the pages router, but I didn't want delete it entirely
…g from GitHub action with yarn build
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.
I acknowledge we have commented out the consent tests.
Our plan is to re-enable them in the near future.
Purpose
Migrate
/doi.org
pages to theapp
routercloses: #333
Approach
I followed a similar approach to the index page migration
Open Questions and Pre-Merge TODOs
src/app/doi
folder.types.ts
file and react-bootstrap wrappers, or adding the'use client'
directivedoi.css
import from the root layout page into thestyles.css
fileSome cypress tests were throwing errors that don't appear when I manually follow the same steps. After spending some time looking into it with no success, I decided to disable them for the time beingexperimentalFetchPolyfill: false
incypress.config.ts
yarn run dev
. However, they work withyarn run build
Learning
Types of changes
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Reviewer, please remember our guidelines: