Skip to content

[Under Beta] Add RHP to workspace room list page - #92096

Merged
grgia merged 12 commits into
Expensify:mainfrom
software-mansion-labs:kuba-nowakowski/feature/workspace-rooms-row-click
Jun 10, 2026
Merged

grgia merged 12 commits into
Expensify:mainfrom
software-mansion-labs:kuba-nowakowski/feature/workspace-rooms-row-click

Conversation

@sumo-slonik

@sumo-slonik sumo-slonik commented May 29, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

On the WorkspaceRoomsPage, tapping a room row now branches by the user's workspace role:

  • Admin → opens the room details RHP (Go to room).
  • Non-admin → navigates directly to the room report.

Still gated by the workspaceRoomsPage beta.

Fixed Issues

$ #89721
$ #89902
PROPOSAL:

Tests

  1. Enable the workspaceRoomsPage beta.
  2. As a policy admin, open a workspace's Rooms page and tap a row → the room details RHP opens with Go to room
  3. As a non-admin of the workspace, open the same page and tap a row → you are navigated directly to the room report.
  • Verify that no errors appear in the JS console

Offline tests

Unnecessary

QA Steps

Same as tests.

  • 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 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

MacOS: Chrome / Safari
Screen.Recording.2026-06-01.at.10.46.32.mov

…-nowakowski/feature/workspace-rooms-row-click

# Conflicts:
#	src/pages/workspace/rooms/WorkspaceRoomsPage.tsx
Match the icon used by the workspace Rooms tab. Drop the auto-generatable
language entries so only en and es are maintained by hand.
@melvin-bot

melvin-bot Bot commented May 29, 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

@sumo-slonik
sumo-slonik force-pushed the kuba-nowakowski/feature/workspace-rooms-row-click branch from a1b14b8 to 942cdef Compare June 1, 2026 07:53
@codecov

codecov Bot commented Jun 1, 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/CONST/index.ts 93.79% <ø> (ø)
src/ROUTES.ts 20.32% <0.00%> (-0.02%) ⬇️
...rc/components/Tables/WorkspaceRoomsTable/index.tsx 0.00% <0.00%> (ø)
src/pages/workspace/rooms/WorkspaceRoomsPage.tsx 0.00% <0.00%> (ø)
src/pages/DynamicReportDetailsPage.tsx 56.02% <57.14%> (-0.10%) ⬇️
... and 26 files with indirect coverage changes

@sumo-slonik
sumo-slonik force-pushed the kuba-nowakowski/feature/workspace-rooms-row-click branch from f6f764f to 568502a Compare June 1, 2026 09:04
@sumo-slonik
sumo-slonik marked this pull request as ready for review June 1, 2026 09:11
@sumo-slonik
sumo-slonik requested review from a team as code owners June 1, 2026 09:11
@sumo-slonik

Copy link
Copy Markdown
Contributor Author

@grgia , can we run automatic translations here?

@melvin-bot
melvin-bot Bot requested review from dukenv0307 and heyjennahay and removed request for a team June 1, 2026 09:11
@melvin-bot

melvin-bot Bot commented Jun 1, 2026

Copy link
Copy Markdown

@dukenv0307 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@dukenv0307

Copy link
Copy Markdown
Contributor

reviewing...

@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: 568502a8dd

ℹ️ 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".

memberCount: getParticipantsAccountIDsForDisplay(report, true, false, false, undefined, personalDetails).length,
action: () => Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(report.reportID)),
action: () => {
const targetRoute = isAdmin ? createDynamicRoute(DYNAMIC_ROUTES.REPORT_DETAILS.getRoute(report.reportID)) : ROUTES.REPORT_WITH_ID.getRoute(report.reportID);

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 Avoid deriving the details route from the active RHP

When an admin has one room details panel open on the workspace Rooms page and selects another visible room row without closing it, createDynamicRoute() defaults to Navigation.getActiveRoute(), which is already the dynamic details URL containing ?reportID=<old>. The new suffix from DYNAMIC_ROUTES.REPORT_DETAILS.getRoute(report.reportID) also contains reportID, so the dynamic-route helper throws on the duplicate query key instead of opening the second room. Build this from the stable rooms base route (or close/replace the current RHP) rather than the current active route.

Useful? React with 👍 / 👎.

@dukenv0307

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I verified proper code patterns were followed (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
    • 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 verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • 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
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Screen.Recording.2026-06-01.at.16.45.41.mov
Android: mWeb Chrome
Screen.Recording.2026-06-01.at.16.40.08.mov
iOS: HybridApp
Screen.Recording.2026-06-01.at.16.42.36.mov
iOS: mWeb Safari
Screen.Recording.2026-06-01.at.16.39.18.mov
MacOS: Chrome / Safari
Screen.Recording.2026-06-01.at.16.35.03.mov

@grgia
grgia self-requested a review June 1, 2026 13:50
@OSBotify

OSBotify commented Jun 1, 2026

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 8bda4e40269..37eba434f04 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -2892,6 +2892,7 @@ ${amount} für ${merchant} – ${date}`,
         waitForPDF: 'Bitte warten, während wir das PDF erstellen.',
         errorPDF: 'Beim Versuch, Ihre PDF zu erstellen, ist ein Fehler aufgetreten',
         successPDF: 'Dein PDF wurde erstellt! Falls es nicht automatisch heruntergeladen wurde, verwende die Schaltfläche unten.',
+        goToRoom: 'Zum Raum gehen',
     },
     reportDescriptionPage: {
         roomDescription: 'Zimmerbeschreibung',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index df8a728dc2a..55a81f91908 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -2900,6 +2900,7 @@ ${amount} pour ${merchant} - ${date}`,
         waitForPDF: 'Veuillez patienter pendant que nous générons le PDF.',
         errorPDF: 'Une erreur s’est produite lors de la tentative de génération de votre PDF',
         successPDF: 'Votre PDF a été généré ! S’il ne s’est pas téléchargé automatiquement, utilisez le bouton ci-dessous.',
+        goToRoom: 'Aller à la salle',
     },
     reportDescriptionPage: {
         roomDescription: 'Description de la salle',
@@ -2976,7 +2977,7 @@ ${amount} pour ${merchant} - ${date}`,
         phoneOrEmail: 'Téléphone ou e-mail',
         error: {
             agentSignInBlocked:
-                'Les comptes d\u2019agent ne permettent pas de se connecter directement. Pour utiliser un agent, connectez-vous avec votre propre compte et accédez-y via Copilot.',
+                'Les comptes d’agent ne permettent pas de se connecter directement. Pour utiliser un agent, connectez-vous avec votre propre compte et accédez-y via Copilot.',
             invalidFormatEmailLogin: 'L’adresse e-mail saisie est invalide. Veuillez corriger le format et réessayer.',
         },
         cannotGetAccountDetails: 'Impossible de récupérer les détails du compte. Veuillez essayer de vous reconnecter.',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 873bd2941bc..cb0fbf816ea 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -2888,6 +2888,7 @@ ${amount} per ${merchant} - ${date}`,
         waitForPDF: 'Attendi mentre generiamo il PDF.',
         errorPDF: 'Si è verificato un errore durante il tentativo di generare il tuo PDF',
         successPDF: 'Il tuo PDF è stato generato! Se non è stato scaricato automaticamente, usa il pulsante qui sotto.',
+        goToRoom: 'Vai alla stanza',
     },
     reportDescriptionPage: {
         roomDescription: 'Descrizione stanza',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index f3200b39434..9369948e517 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -2864,6 +2864,7 @@ ${date} の ${merchant} への ${amount}`,
         waitForPDF: 'PDF を作成しています。しばらくお待ちください。',
         errorPDF: 'PDF の生成中にエラーが発生しました',
         successPDF: 'PDFが作成されました!自動的にダウンロードされない場合は、下のボタンを使用してください。',
+        goToRoom: 'ルームに移動',
     },
     reportDescriptionPage: {
         roomDescription: '部屋の説明',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 92edd92d3d6..80a4aa5336c 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -2885,6 +2885,7 @@ ${amount} voor ${merchant} - ${date}`,
         waitForPDF: 'Even geduld terwijl we de pdf genereren.',
         errorPDF: 'Er is een fout opgetreden bij het genereren van je PDF',
         successPDF: 'Je PDF is gegenereerd! Als het niet automatisch is gedownload, gebruik dan de knop hieronder.',
+        goToRoom: 'Ga naar kamer',
     },
     reportDescriptionPage: {
         roomDescription: 'Kamerbeschrijving',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 42b105e62d4..ff8291fc149 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -2879,6 +2879,7 @@ ${amount} dla ${merchant} - ${date}`,
         waitForPDF: 'Poczekaj, aż wygenerujemy plik PDF.',
         errorPDF: 'Wystąpił błąd podczas próby wygenerowania Twojego pliku PDF',
         successPDF: 'Twój plik PDF został wygenerowany! Jeśli nie pobrał się automatycznie, użyj przycisku poniżej.',
+        goToRoom: 'Przejdź do pokoju',
     },
     reportDescriptionPage: {
         roomDescription: 'Opis pokoju',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index ab3f8e49e2d..fb07eb58818 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -2879,6 +2879,7 @@ ${amount} para ${merchant} - ${date}`,
         waitForPDF: 'Aguarde enquanto geramos o PDF.',
         errorPDF: 'Ocorreu um erro ao tentar gerar seu PDF',
         successPDF: 'Seu PDF foi gerado! Se ele não foi baixado automaticamente, use o botão abaixo.',
+        goToRoom: 'Ir para a sala',
     },
     reportDescriptionPage: {
         roomDescription: 'Descrição do quarto',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index b28aeef66f6..1f0599d5386 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -2807,6 +2807,7 @@ ${amount},商户:${merchant} - 日期:${date}`,
         waitForPDF: '正在生成 PDF,请稍候。',
         errorPDF: '尝试生成您的 PDF 时出错',
         successPDF: '您的 PDF 已生成!如果没有自动下载,请使用下面的按钮。',
+        goToRoom: '进入房间',
     },
     reportDescriptionPage: {
         roomDescription: '房间描述',

Note

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

View workflow run

@grgia

grgia commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

@sumo-slonik would you push translations/merge main

@grgia

grgia commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Thanks @sumo-slonik I'm afk for the next hour or so but will retest once im at the airport!

@sumo-slonik

Copy link
Copy Markdown
Contributor Author

Thanks @sumo-slonik I'm afk for the next hour or so but will retest once im at the airport!

thanks!

@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

grgia
grgia previously approved these changes Jun 4, 2026
@grgia

grgia commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

@sumo-slonik conflicts 🙇

…click

# Conflicts:
#	src/components/Tables/WorkspaceRoomsTable/index.tsx
@sumo-slonik

Copy link
Copy Markdown
Contributor Author

@grgia it seems to me we’re ready to merge. I resolved the conflicts

@grgia grgia changed the title Add RHP to workspace room list page [Under Beta] Add RHP to workspace room list page Jun 10, 2026
@grgia
grgia merged commit d0aa84f into Expensify:main Jun 10, 2026
35 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/grgia in version: 9.4.5-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Help site review: no changes required.

What this PR does: On the Workspace Rooms page (gated behind the workspaceRoomsPage beta), tapping a room row now branches by role — admins open the room details RHP (with a new Go to room item), and non-admins navigate straight to the room report. It also adds the goToRoom translation key and minor layout padding.

Why no docs update is needed:

  • The behavior is gated behind the workspaceRoomsPage beta, so it isn't generally available to document yet.
  • This is an internal navigation/UX nuance (where a row tap lands based on role), not a new user-facing workflow.
  • No existing help article under docs/articles documents the Workspace Rooms list page or its row-tap navigation, so nothing on the help site becomes inaccurate. The closest article, Admin Rooms in Expensify Chat, covers the #announce and #admins rooms and is unaffected by this change.

If/when this feature graduates out of beta, the Workspace Rooms list page may be worth documenting at that point.


@sumo-slonik, no help site PR was created since no documentation changes are required for this beta-gated change. If you believe the Workspace Rooms page should be documented now, let me know and I'll draft a PR.

@mitarachim

Copy link
Copy Markdown

Deploy Blocker #93248 was identified to be related to this PR.

@mitarachim

Copy link
Copy Markdown

Deploy Blocker #93257 was identified to be related to this PR.

@Julesssss

Copy link
Copy Markdown
Contributor

Deploy Blocker #93248 was identified to be related to this PR.

Resolved.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.5-6 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

// Only show the "Go to room" row when the Details page was opened from a screen other than the room report itself (e.g. the Workspace rooms list).
const isRoomCurrentlyOpen = isReportTopmostSplitNavigator() && Navigation.getTopmostReportId() === report?.reportID;
const shouldShowGoToRoom = (isChatRoom || isPolicyExpenseChat) && !isRoomCurrentlyOpen;
const shouldShowGoToWorkspace = shouldShowPolicy(policy, false, currentUserPersonalDetails?.email) && !policy?.isJoinRequestPending && !shouldShowGoToRoom;

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.

Coming from #93257

isRoomCurrentlyOpen reads live navigation state during render. When "Go to room" is tapped, getTopmostReportId() updates before the RHP closes, so the row flips to "Go to workspace" briefly.

Fixed in #93296 by snapshotting this on focus instead of reading it reactively during the transition.

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.