-
Notifications
You must be signed in to change notification settings - Fork 0
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
Spike: Layout/breadcrumbs in Pages router #144
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
src/pages/collections/[id].tsx
Outdated
); | ||
}; | ||
|
||
// Imagine an API call somewhere in 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.
Have you tried passing this mocked API-fetched data to the component? How would this change if you use this breadcrumbs
array as a prop in Collection
, i.e. const Collection = ({ breadcrumbs }) => {....
.
You could use the last object in the array as the value that is passed to setBreadcrumbs
.
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.
Right, sorry for the confusion of trying to represent two approaches within the same file but yes imagining that as a prop to Collections
. If that's the case though, I wouldn't use the context at all
Ticket:
Investigates DR-2966.
This PR does the following:
Layout
component that contains header, DS provider, feedback, etcLayout
to all pages/divisions/[slug]
,/collections/[slug]
,/divisions
,/collections
How has this been tested?
Accessibility concerns or updates
Checklist: