-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Revert "chore: refactor the generateBlogData
function (#7607)"
#7617
Merged
ovflowd
merged 1 commit into
nodejs:main
from
dario-piotrowicz:dario/revert-generateBlogData-change
Apr 3, 2025
Merged
Revert "chore: refactor the generateBlogData
function (#7607)"
#7617
ovflowd
merged 1 commit into
nodejs:main
from
dario-piotrowicz:dario/revert-generateBlogData-change
Apr 3, 2025
+44
−40
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit b7364b9.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (1)
apps/site/next-data/generators/blogData.mjs:80
- [nitpick] Using an array to store the frontmatter with string keys is non-standard, which may be confusing. Consider using an object or Map for clearer intent when keying by filename.
rawFrontmatter[filename] = [0, ''];
bjohansebas
approved these changes
Apr 3, 2025
Lighthouse Results
|
Fast-tracking as it is affecting production! |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts commit b7364b9.
Description
My change in #7607 actually causes blog tabs to 404s 😓
I'm really sorry for this, I must admit that I did not check my changes with
next build
+next start
but only withnext dev
and my changes work perfectly fine with the latter 😓Since this effecting the production site I would assume that this need to be reverted asap, I'll anyways look into the issue and try to re-land the refactoring afterwords
Validation
Related Issues
Check List
npm run format
to ensure the code follows the style guide.npm run test
to check if all tests are passing.npx turbo build
to check if the website builds without errors.