Railway Deployment #1b4f3f fix: guard undefined body in about page - #76
Merged
Merged
Conversation
This file contains hidden or 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
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.
Problem
The build failed during Next.js's TypeScript type-check step with "Type error: 'body' is possibly 'undefined'" in app/[locale]/about/page.tsx. The strikes type in lib/i18n/dictionary.ts defines body as an optional string[], but the inline JSX replacing StoryCarousel called body.map() directly without a null check.
Solution
Changed body.map(...) to (body ?? []).map(...) to narrow the type to string[] before calling map, satisfying strict null checks while preserving identical runtime behavior.
Changes
app/[locale]/about/page.tsxContext
0e47825Generated by Railway