Skip to content

[Home Page] Create ForYouSection Component (1/2) - Preparing the Home Page layout - #80555

Closed
adamgrzybowski wants to merge 4 commits into
Expensify:mainfrom
software-mansion-labs:home-page/initial-layout
Closed

adamgrzybowski wants to merge 4 commits into
Expensify:mainfrom
software-mansion-labs:home-page/initial-layout

Conversation

@adamgrzybowski

@adamgrzybowski adamgrzybowski commented Jan 27, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Note

Wait for the #80571 to be merged

This PR adds the common parts for all HomePage sections:

  • Two-column responsive layout
  • WidgetContainer component for consistent section styling
  • Placeholder sections: AtGlanceSection, DiscoverSection, AnnouncementsSection

Splitting the common parts from the AtGlanceSection-specific implementation allows parallel work on individual sections while the common parts are being reviewed.

The placeholder content will be replaced with actual implementations in follow-up PRs.

Fixed Issues

$ #79979
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-01-26.at.15.46.57.mp4

@melvin-bot

melvin-bot Bot commented Jan 27, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@adamgrzybowski adamgrzybowski changed the title [Home Page] Create AtAGlanceSection Component (1/2) - Preparing the Home Page layout [Hold #80571][Home Page] Create AtAGlanceSection Component (1/2) - Preparing the Home Page layout Jan 27, 2026
@adamgrzybowski
adamgrzybowski force-pushed the home-page/initial-layout branch from ae666fd to af184a9 Compare January 27, 2026 01:57
@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 336bf871..3f8387ea 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -8038,7 +8038,7 @@ Hier ist ein *Testbeleg*, um dir zu zeigen, wie es funktioniert:`,
         domainAdmins: 'Domain-Admins',
     },
     gps: {
-        tooltip: 'GPS-Verfolgung läuft! Wenn du fertig bist, stoppe die Verfolgung unten.',
+        tooltip: 'GPS-Tracking läuft! Wenn du fertig bist, beende das Tracking unten.',
         disclaimer: 'Benutze GPS, um eine Ausgabe von deiner Reise zu erstellen. Tippe unten auf „Start“, um mit der Aufzeichnung zu beginnen.',
         error: {failedToStart: 'Standortverfolgung konnte nicht gestartet werden.', failedToGetPermissions: 'Die erforderlichen Standortberechtigungen konnten nicht abgerufen werden.'},
         trackingDistance: 'Strecke wird verfolgt...',
@@ -8085,6 +8085,7 @@ Hier ist ein *Testbeleg*, um dir zu zeigen, wie es funktioniert:`,
         },
         fabGpsTripExplained: 'Zur GPS-Ansicht wechseln (Schnellaktion)',
     },
+    homePage: {atAGlance: 'Auf einen Blick', reportsToReview: 'Berichte zur Überprüfung', announcements: 'Ankündigungen', discover: 'Entdecken'},
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
 // so if you change it here, please update it there as well.
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index c80f7a1d..300f74e9 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -8044,7 +8044,7 @@ Voici un *reçu test* pour vous montrer comment cela fonctionne :`,
         domainAdmins: 'Administrateurs de domaine',
     },
     gps: {
-        tooltip: 'Suivi GPS en cours ! Quand vous avez terminé, arrêtez le suivi ci-dessous.',
+        tooltip: 'Suivi GPS en cours ! Lorsque vous avez terminé, arrêtez le suivi ci-dessous.',
         disclaimer: 'Utilisez le GPS pour créer une dépense à partir de votre trajet. Touchez Démarrer ci-dessous pour commencer le suivi.',
         error: {failedToStart: 'Impossible de démarrer le suivi de la localisation.', failedToGetPermissions: 'Échec de l’obtention des autorisations de localisation requises.'},
         trackingDistance: 'Suivi de la distance...',
@@ -8091,6 +8091,7 @@ Voici un *reçu test* pour vous montrer comment cela fonctionne :`,
         },
         fabGpsTripExplained: 'Aller à l’écran GPS (action flottante)',
     },
+    homePage: {atAGlance: 'En un coup d’œil', reportsToReview: 'Rapports à examiner', announcements: 'Annonces', discover: 'Découvrir'},
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
 // so if you change it here, please update it there as well.
diff --git a/src/languages/it.ts b/src/languages/it.ts
index c4668644..4fe03d92 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -6878,7 +6878,7 @@ Richiedi dettagli di spesa come ricevute e descrizioni, imposta limiti e valori
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: 'Da',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'Carta',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID prelievo',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID prelievo', //_/\__/_/  \_,_/\__/\__/\_,_/
             },
             feed: 'Feed',
             withdrawalType: {
@@ -8073,6 +8073,7 @@ Ecco una *ricevuta di prova* per mostrarti come funziona:`,
         },
         fabGpsTripExplained: 'Vai alla schermata GPS (azione flottante)',
     },
+    homePage: {atAGlance: 'A colpo d’occhio', reportsToReview: 'Report da esaminare', announcements: 'Annunci', discover: 'Scopri'},
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
 // so if you change it here, please update it there as well.
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index cbe74fca..e5d6f818 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -6819,7 +6819,7 @@ ${reportName}
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: '差出人',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'カード',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '出金ID',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '出金 ID',
             },
             feed: 'フィード',
             withdrawalType: {
@@ -7960,7 +7960,7 @@ Expensify の使い方をお見せするための*テストレシート*がこ
         domainAdmins: 'ドメイン管理者',
     },
     gps: {
-        tooltip: 'GPS 追跡を進行中です!完了したら、下で追跡を停止してください。',
+        tooltip: 'GPS追跡を実行中です!完了したら、下で追跡を停止してください。',
         disclaimer: '移動中の経路から、GPS を使って経費を作成しましょう。下の「開始」をタップして追跡を始めてください。',
         error: {failedToStart: '位置情報の追跡を開始できませんでした。', failedToGetPermissions: '必要な位置情報の権限を取得できませんでした。'},
         trackingDistance: '距離を追跡中...',
@@ -7987,6 +7987,7 @@ Expensify の使い方をお見せするための*テストレシート*がこ
         },
         fabGpsTripExplained: 'GPS画面へ移動(フローティングアクション)',
     },
+    homePage: {atAGlance: '一目で分かる', reportsToReview: 'レビュー対象のレポート', announcements: 'お知らせ', discover: '発見'},
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
 // so if you change it here, please update it there as well.
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index d07a6f98..395e6fbc 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -8047,6 +8047,7 @@ Hier is een *testbon* om je te laten zien hoe het werkt:`,
         },
         fabGpsTripExplained: 'Ga naar GPS-scherm (Zwevende actie)',
     },
+    homePage: {atAGlance: 'In één oogopslag', reportsToReview: 'Rapporten om te beoordelen', announcements: 'Aankondigingen', discover: 'Ontdekken'},
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
 // so if you change it here, please update it there as well.
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 08e2d8bb..0162fa0f 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -6849,7 +6849,7 @@ Wymagaj szczegółów wydatków, takich jak paragony i opisy, ustawiaj limity i
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: 'Od',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'Karta',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID wypłaty',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'Identyfikator wypłaty',
             },
             feed: 'Kanał',
             withdrawalType: {
@@ -8034,6 +8034,7 @@ Oto *paragon testowy*, który pokazuje, jak to działa:`,
         },
         fabGpsTripExplained: 'Przejdź do ekranu GPS (przycisk akcji)',
     },
+    homePage: {atAGlance: 'W skrócie', reportsToReview: 'Raporty do sprawdzenia', announcements: 'Ogłoszenia', discover: 'Odkryj'},
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
 // so if you change it here, please update it there as well.
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index cfcc64eb..099221a0 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -6851,7 +6851,7 @@ Exija detalhes de despesas como recibos e descrições, defina limites e padrõe
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: 'De',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'Cartão',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID de saque',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID de retirada',
             },
             feed: 'Feed',
             withdrawalType: {
@@ -7997,7 +7997,7 @@ Aqui está um *recibo de teste* para mostrar como funciona:`,
         domainAdmins: 'Administradores de domínio',
     },
     gps: {
-        tooltip: 'Rastreamento por GPS em andamento! Quando terminar, pare o rastreamento abaixo.',
+        tooltip: 'Rastreamento de GPS em andamento! Quando terminar, pare o rastreamento abaixo.',
         disclaimer: 'Use o GPS para criar uma despesa a partir da sua viagem. Toque em Iniciar abaixo para começar o rastreamento.',
         error: {failedToStart: 'Falha ao iniciar o rastreamento de localização.', failedToGetPermissions: 'Falha ao obter as permissões de localização necessárias.'},
         trackingDistance: 'Acompanhando a distância...',
@@ -8044,6 +8044,7 @@ Aqui está um *recibo de teste* para mostrar como funciona:`,
         },
         fabGpsTripExplained: 'Ir para a tela de GPS (Ação flutuante)',
     },
+    homePage: {atAGlance: 'De relance', reportsToReview: 'Relatórios para revisar', announcements: 'Comunicados', discover: 'Descobrir'},
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
 // so if you change it here, please update it there as well.
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index c3824768..de6ea6bf 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6698,9 +6698,9 @@ ${reportName}
             reimbursable: '可报销',
             purchaseCurrency: '购买货币',
             groupBy: {
-                [CONST.SEARCH.GROUP_BY.FROM]: '从',
-                [CONST.SEARCH.GROUP_BY.CARD]: '卡片',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '提款 ID',
+                [CONST.SEARCH.GROUP_BY.FROM]: '来自',
+                [CONST.SEARCH.GROUP_BY.CARD]: '卡',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '提现 ID',
             },
             feed: '动态',
             withdrawalType: {
@@ -7822,6 +7822,7 @@ ${reportName}
         locationServicesRequiredModal: {title: '需要访问位置信息', confirm: '打开设置', prompt: '请在设备设置中允许位置访问,以开始 GPS 距离跟踪。'},
         fabGpsTripExplained: '前往 GPS 屏幕(悬浮操作)',
     },
+    homePage: {atAGlance: '一览', reportsToReview: '待审核报表', announcements: '公告', discover: '发现'},
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
 // so if you change it here, please update it there as well.

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

@@ -552,7 +559,7 @@ function AuthScreens() {
/>
<RootStack.Screen
name={SCREENS.WORKSPACES_LIST}
options={rootNavigatorScreenOptions.workspacesListPage}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you explain this change?

@github-actions

Copy link
Copy Markdown
Contributor

🚧 @grgia has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

Copy link
Copy Markdown
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #80555.

Android 🤖 iOS 🍎
❌ FAILED ❌ ❌ FAILED ❌
The QR code can't be generated, because the Android build failed The QR code can't be generated, because the iOS build failed
Web 🕸️
❌ FAILED ❌
The QR code can't be generated, because the Web build failed

👀 View the workflow run that generated this build 👀

@grgia grgia changed the title [Hold #80571][Home Page] Create AtAGlanceSection Component (1/2) - Preparing the Home Page layout [Home Page] Create AtAGlanceSection Component (1/2) - Preparing the Home Page layout Jan 28, 2026
@grgia

grgia commented Jan 28, 2026

Copy link
Copy Markdown
Contributor

Removed hold, awaiting merge main @adamgrzybowski

@grgia grgia left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's rename ForYouSection

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

@adamgrzybowski
Could you please update the branch to the latest version of main when you are free?

@adamgrzybowski
adamgrzybowski force-pushed the home-page/initial-layout branch from 32cdab6 to 8e838cd Compare January 28, 2026 18:30
Comment thread src/libs/Permissions.ts Outdated
@@ -16,6 +16,7 @@ function canUseLinkPreviews(): boolean {
}

function isBetaEnabled(beta: Beta, betas: OnyxEntry<Beta[]>, betaConfiguration?: OnyxEntry<BetaConfiguration>): boolean {
return true;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we don't need these changes😅

// Select a random empty state message on mount (will change on refresh/remount)
const emptyStateMessage = useMemo(
// eslint-disable-next-line @typescript-eslint/no-non-null-assertion, react-hooks/purity
() => EMPTY_STATE_MESSAGES.at(Math.floor(Math.random() * EMPTY_STATE_MESSAGES.length))!,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose it's a temporary message
Let's add TODO to not forget about it

const payCount = reportCounts[CONST.SEARCH.SEARCH_KEYS.PAY];
const exportCount = reportCounts[CONST.SEARCH.SEARCH_KEYS.EXPORT];

const hasAnyTodos = submitCount > 0 || approveCount > 0 || payCount > 0 || exportCount > 0;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe just const hasAnyTodos = submitCount || approveCount || payCount || exportCount; ?

@adamgrzybowski
adamgrzybowski force-pushed the home-page/initial-layout branch from 8e838cd to bdcfe5e Compare January 28, 2026 19:25
@codecov

codecov Bot commented Jan 28, 2026

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/libs/Navigation/AppNavigator/AuthScreens.tsx 53.12% <100.00%> (ø)
src/styles/variables.ts 100.00% <ø> (ø)
src/pages/home/AnnouncementsSection.tsx 0.00% <0.00%> (ø)
src/pages/home/DiscoverSection.tsx 0.00% <0.00%> (ø)
src/components/WidgetContainer.tsx 0.00% <0.00%> (ø)
src/styles/index.ts 42.93% <0.00%> (-2.21%) ⬇️
src/pages/home/ForYouSection.tsx 0.00% <0.00%> (ø)
src/pages/home/HomePage.tsx 0.00% <0.00%> (ø)
... and 43 files with indirect coverage changes

Comment on lines +12 to +21
/** The icon to display along with the title */
icon?: IconAsset;

/** The text to display in the title of the widget */
title?: string;

/** Custom color for the title text */
titleColor?: string;

/** The width of the icon. */

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just thinking
Maybe we should just pass the icon as a parameter?
Instead of three parameters

@mountiny mountiny changed the title [Home Page] Create AtAGlanceSection Component (1/2) - Preparing the Home Page layout [Home Page] Create ForYouSection Component (1/2) - Preparing the Home Page layout Jan 28, 2026
@mountiny

Copy link
Copy Markdown
Contributor

@codex review

@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

We don't need this one. These changes will go with the first widget, because it's ready for review.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3e250e8b19

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/languages/en.ts
Comment on lines +991 to +995
homePage: {
forYou: 'For you',
announcements: 'Announcements',
discover: 'Discover',
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add homePage strings to all locales

Only en and es define the new homePage.* keys, but translate() (see src/libs/Localize/index.ts) throws in dev and returns the raw path / missing translation sentinel in staging/production when a key is missing for the active locale. That means users on any other locale (e.g. fr/de/pt-BR) will see homePage.forYou/homePage.discover instead of readable titles on the Home page. Please add the new keys to all language files (or a proper fallback) to avoid missing-translation behavior.

Useful? React with 👍 / 👎.

Comment on lines +77 to +79
<Button
text="Go to submitted expense reports"
onPress={handleGoToSearch}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Localize For You button labels

These button labels are hard-coded English strings, so users in non-English locales will always see English text even when the app is localized. This is user-facing and inconsistent with the rest of the Home page, which uses translate(). Please add translation keys and use translate() for these labels.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants