-
Notifications
You must be signed in to change notification settings - Fork 75
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
News Site Next #426
base: main
Are you sure you want to change the base?
News Site Next #426
Conversation
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.
Generally LGTM: might be worth adding a little test to check for consistency across languages and uniqueness of IDs within a language.
yes, absolutely! |
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 looks good to me, thanks for the fix.
One more thing: in section.jsx
you can use article.id
instead of concatenating the section id with index
.
Do we have before/after numbers? |
here's a snapshot
|
Is that runtime or pts? |
we're displaying runtime in the detail screen, right? |
@rniwa - any concerns to merge this? |
This fixes next.js issue: #422
A separate pr for Nuxt will do the same.
The fix here is to add unique ids to any article content that is a list.
This is done in the actual data files, so no need for the app to generate them at any point.
@kara