Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughImplements the home tab screen with personalized greeting from Clerk user data, daily XP progress tracking, current lesson/unit selection from store-driven language choice, new image asset constants, and a "Today's plan" section composed of reusable PlanRow components displaying task icons, titles, and completion indicators. ChangesHome Screen Dashboard
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
app/(tabs)/home.tsx (1)
177-221: ⚡ Quick winMove
PlanRowout of the screen into a reusable component file.This block is a reusable UI section and makes the screen file heavier than necessary.
As per coding guidelines, "Screens should compose components and call hooks/stores, but should not contain large reusable UI blocks or complex business logic".
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@app/`(tabs)/home.tsx around lines 177 - 221, The PlanRow component (PlanRow and PlanRowProps) is a reusable UI block and should be moved out of the screen file into its own component file; create a new component file (e.g., PlanRow.tsx) that exports PlanRow as default, copy the PlanRow and PlanRowProps definitions plus any local style references (or refactor styles.planIcon into the new file or import shared styles), keep the same prop defaults (isComplete, variant) and Ionicons usage, then replace the inline definition in home.tsx with an import of the new PlanRow component and ensure any TypeScript types and styling imports are updated so the screen composes the component without duplicating logic.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@app/`(tabs)/home.tsx:
- Around line 192-197: Replace dynamic NativeWind class concatenation for the
icon background and the other conditional classes by computing plain style
values and passing them via the style prop or a StyleSheet instead of embedding
them in className; for example, remove iconBackground (the string built from
variant === "coral" ? "bg-[`#FF515B`]" : "bg-lingua-deep-purple") and create an
iconBackgroundColor variable (e.g., variant === "coral" ? "`#FF515B`" : "`#2F2064`")
then keep the static className on the View
(h/w/rounded/items-center/justify-center) and add style={{ backgroundColor:
iconBackgroundColor }}; apply the same approach to the other conditional class
usage (the ternary used around lines 213-215) by computing the corresponding
color/font-size/etc. value and moving it into style or a StyleSheet entry
referenced by that component.
- Around line 74-80: The Pressable elements (e.g., the Pressable wrapping
Ionicons in app/(tabs)/home.tsx and the other Pressable controls at the ranges
reported) are interactive but lack onPress handlers; wire them to real handlers
using Expo Router or render non-interactive Views. For each Pressable (identify
by the Pressable component instances and the icons they wrap, e.g., the
notifications Ionicons), import and use useRouter() from "expo-router" and add
an onPress that calls router.push(...) to the appropriate route or call the
intended handler function, or replace the Pressable with a plain View/Text when
no action is required. Ensure hitSlop, accessibilityLabel and pressed style are
preserved and update any tests/components expecting navigation to point to the
new routes.
In `@constants/images.ts`:
- Around line 32-34: Replace the remote URI in the images object for
teacherPortrait with a bundled import/require so the asset is deterministic and
available offline: add an import or require for the teacher portrait asset at
the top of constants/images.ts (e.g., const teacherPortraitImg =
require('./path/to/teacherPortrait.png') or import teacherPortraitImg from
'...'), then update the teacherPortrait entry in the exported images object to
use that imported value instead of the remote uri string; keep the property name
teacherPortrait unchanged so other modules referencing images.teacherPortrait
continue to work.
---
Nitpick comments:
In `@app/`(tabs)/home.tsx:
- Around line 177-221: The PlanRow component (PlanRow and PlanRowProps) is a
reusable UI block and should be moved out of the screen file into its own
component file; create a new component file (e.g., PlanRow.tsx) that exports
PlanRow as default, copy the PlanRow and PlanRowProps definitions plus any local
style references (or refactor styles.planIcon into the new file or import shared
styles), keep the same prop defaults (isComplete, variant) and Ionicons usage,
then replace the inline definition in home.tsx with an import of the new PlanRow
component and ensure any TypeScript types and styling imports are updated so the
screen composes the component without duplicating logic.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: f7748b8d-d291-446d-812e-03fbf587bf68
📒 Files selected for processing (2)
app/(tabs)/home.tsxconstants/images.ts
Comment on lines
+74
to
+80
| <Pressable | ||
| accessibilityLabel="Notifications" | ||
| hitSlop={12} | ||
| style={({ pressed }) => pressed && styles.pressed} | ||
| > | ||
| <Ionicons name="notifications-outline" size={30} color="#0D132B" /> | ||
| </Pressable> |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n app/\(tabs\)/home.tsx | head -200Repository: Retsomm/react-native-lingua
Length of output: 8866
🏁 Script executed:
cat -n app/\(tabs\)/home.tsx | grep -E "(import|useRouter|router)" | head -20Repository: Retsomm/react-native-lingua
Length of output: 605
🏁 Script executed:
cat -n app/\(tabs\)/home.tsx | tail -50Repository: Retsomm/react-native-lingua
Length of output: 1748
Wire all Pressable controls to real handlers (or render non-interactive views).
Lines 74-80, 130-138, and 145-149 render tappable UI with no onPress handlers, making these controls non-functional despite button affordance. According to the coding guidelines for app/**/*.{ts,tsx}, use Expo Router for navigation and wire these to appropriate routes or handlers.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@app/`(tabs)/home.tsx around lines 74 - 80, The Pressable elements (e.g., the
Pressable wrapping Ionicons in app/(tabs)/home.tsx and the other Pressable
controls at the ranges reported) are interactive but lack onPress handlers; wire
them to real handlers using Expo Router or render non-interactive Views. For
each Pressable (identify by the Pressable component instances and the icons they
wrap, e.g., the notifications Ionicons), import and use useRouter() from
"expo-router" and add an onPress that calls router.push(...) to the appropriate
route or call the intended handler function, or replace the Pressable with a
plain View/Text when no action is required. Ensure hitSlop, accessibilityLabel
and pressed style are preserved and update any tests/components expecting
navigation to point to the new routes.
This was referenced May 19, 2026
Merged
Merged
Merged
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
1 participant
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.
Summary by CodeRabbit
New Features
Assets