Skip to content

refactor(ui-contexts,fuselage-ui-kit,ui-client): Decouple room navigation hooks from roomCoordinator and ui-contexts#41508

Open
tassoevan wants to merge 4 commits into
developfrom
refactor/room-navigation-hooks
Open

refactor(ui-contexts,fuselage-ui-kit,ui-client): Decouple room navigation hooks from roomCoordinator and ui-contexts#41508
tassoevan wants to merge 4 commits into
developfrom
refactor/room-navigation-hooks

Conversation

@tassoevan

@tassoevan tassoevan commented Jul 22, 2026

Copy link
Copy Markdown
Member

Proposed changes (including videos or screenshots)

Continues the migration off the Meteor-coupled roomCoordinator for room navigation:

  • Replaces roomCoordinator usage in ParentDiscussion and RoomForewordUsernameList with a new useRoomRoute hook (navigates using room data already at hand, no API call).
  • Moves useGoToRoom out of @rocket.chat/ui-contexts into @rocket.chat/fuselage-ui-kit, next to its only consumer (VideoConferenceBlock), since it doesn't need to be a public ui-contexts hook.
  • Moves useRoomRoute out of @rocket.chat/ui-contexts into @rocket.chat/ui-client, next to its only consumer (ParentDiscussion), for the same reason.

No behavior changes for end users.

Issue(s)

Steps to test or reproduce

  • yarn build, yarn turbo run typecheck --force, and yarn testunit all pass.
  • Open a room with a parent discussion and confirm navigating back to the parent room still works.
  • Trigger a video conference message block and confirm "Join discussion" navigation still works.

Further comments

Review in cubic

Task: ARCH-2288

Summary by CodeRabbit

  • New Features

    • Added streamlined routing support for room and discussion navigation, including consistent channel/private/DM link generation.
    • Video conference navigation now uses the shared room-routing logic for more uniform destinations.
  • Bug Fixes

    • Improved “back to room” behavior and room-title computation from discussion context, including correct handling for federated rooms and special-character room name rules.
  • Tests

    • Added unit tests covering navigation behavior for supported room types and cases where room info is unavailable.

cardoso and others added 3 commits July 22, 2026 00:42
Adds a useRoomRoute hook to ui-contexts for navigating to a room from
data already at hand (no API call, unlike useGoToRoom) and uses it in
ParentDiscussion and RoomForewordUsernameList, removing their dependency
on the Meteor-coupled roomCoordinator.
useGoToRoom was only consumed by VideoConferenceBlock, so it doesn't
need to be a public ui-contexts hook. Moved it next to its sole
consumer and dropped the export from @rocket.chat/ui-contexts.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
useRoomRoute was only consumed by ParentDiscussion, a ui-client
component, so it doesn't need to be a public ui-contexts hook. Moved
it into ui-client and dropped the export from @rocket.chat/ui-contexts.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@tassoevan
tassoevan requested a review from a team as a code owner July 22, 2026 03:43
@dionisio-bot

dionisio-bot Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Looks like this PR is not ready to merge, because of the following issues:

  • This PR is missing the 'stat: QA assured' label

Please fix the issues and try again

If you have any trouble, please check the PR guidelines

@changeset-bot

changeset-bot Bot commented Jul 22, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: dd3402b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@tassoevan tassoevan added this to the 8.8.0 milestone Jul 22, 2026
@tassoevan

Copy link
Copy Markdown
Member Author

/jira ARCH-2200

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0209da07-695f-4e79-b39e-a209384a5e00

📥 Commits

Reviewing files that changed from the base of the PR and between 1bbc968 and dd3402b.

📒 Files selected for processing (1)
  • apps/meteor/client/views/room/Header/ParentRoom/ParentDiscussion/ParentDiscussion.tsx
📜 Recent review details
⏰ Context from checks skipped due to timeout. (5)
  • GitHub Check: 📦 Build Packages
  • GitHub Check: cubic · AI code reviewer
  • GitHub Check: CodeQL-Build
  • GitHub Check: Hacktron Security Check
  • GitHub Check: CodeQL-Build
⚠️ CI failures not shown inline (5)

GitHub Check: Dionisio QA: Some checks did not pass

Conclusion: failure

View job details

**Conclusion:** failure
### Steps
- ✅ **No merge conflicts**
- ❌ **QA assured** — This PR is missing the 'stat: QA assured' label
- ✅ **Mergeable**
- ✅ **Has milestone or project**
- ✅ **Valid PR title**
- ✅ **Correct target version**

GitHub Check: Dionisio QA: Some checks did not pass

Conclusion: failure

View job details

**Conclusion:** failure
### Steps
- ✅ **No merge conflicts**
- ❌ **QA assured** — This PR is missing the 'stat: QA assured' label
- ✅ **Mergeable**
- ✅ **Has milestone or project**
- ✅ **Valid PR title**
- ✅ **Correct target version**

GitHub Check: Dionisio QA: Some checks did not pass

Conclusion: failure

View job details

**Conclusion:** failure
### Steps
- ✅ **No merge conflicts**
- ❌ **QA assured** — This PR is missing the 'stat: QA assured' label
- ✅ **Mergeable**
- ✅ **Has milestone or project**
- ✅ **Valid PR title**
- ✅ **Correct target version**

GitHub Check: Dionisio QA: Some checks did not pass

Conclusion: failure

View job details

**Conclusion:** failure
### Steps
- ✅ **No merge conflicts**
- ❌ **QA assured** — This PR is missing the 'stat: QA assured' label
- ✅ **Mergeable**
- ✅ **Has milestone or project**
- ✅ **Valid PR title**
- ✅ **Correct target version**

GitHub Check: Dionisio QA: Some checks did not pass

Conclusion: failure

View job details

**Conclusion:** failure
### Steps
- ✅ **No merge conflicts**
- ❌ **QA assured** — This PR is missing the 'stat: QA assured' label
- ✅ **Mergeable**
- ✅ **Has milestone or project**
- ✅ **Valid PR title**
- ✅ **Correct target version**
🧰 Additional context used
📓 Path-based instructions (1)
**/*.{ts,tsx,js}

📄 CodeRabbit inference engine (.cursor/rules/playwright.mdc)

**/*.{ts,tsx,js}: Write concise, technical TypeScript/JavaScript with accurate typing in Playwright tests
Avoid code comments in the implementation

Files:

  • apps/meteor/client/views/room/Header/ParentRoom/ParentDiscussion/ParentDiscussion.tsx
🧠 Learnings (2)
📚 Learning: 2026-03-27T14:52:56.865Z
Learnt from: dougfabris
Repo: RocketChat/Rocket.Chat PR: 39892
File: apps/meteor/client/views/room/contextualBar/Threads/Thread.tsx:150-155
Timestamp: 2026-03-27T14:52:56.865Z
Learning: In Rocket.Chat, there are two different `ModalBackdrop` components with different prop APIs. During review, confirm the import source: (1) `rocket.chat/fuselage` `ModalBackdrop` uses `ModalBackdropProps` based on `BoxProps` (so it supports `onClick` and other Box/DOM props) and does not have an `onDismiss` prop; (2) `rocket.chat/ui-client` `ModalBackdrop` uses a narrower props interface like `{ children?: ReactNode; onDismiss?: () => void }` and handles Escape keypress and outside mouse-up, and it does not forward arbitrary DOM props such as `onClick`. Flag mismatched props (e.g., `onDismiss` passed to the fuselage component or `onClick` passed to the ui-client component) and ensure the usage matches the correct component being imported.

Applied to files:

  • apps/meteor/client/views/room/Header/ParentRoom/ParentDiscussion/ParentDiscussion.tsx
📚 Learning: 2026-05-06T12:21:44.083Z
Learnt from: juliajforesti
Repo: RocketChat/Rocket.Chat PR: 40256
File: apps/meteor/client/components/CreateDiscussion/CreateDiscussion.tsx:121-149
Timestamp: 2026-05-06T12:21:44.083Z
Learning: Field wrappers in rocket.chat/fuselage-forms (Field, FieldLabel, FieldRow, FieldError, FieldHint) auto-create htmlFor/id associations, aria-describedby, and role="alert" for errors. Do not manually set htmlFor, id, aria-describedby, or role attributes when using these wrappers. This automatic wiring does not apply to plain rocket.chat/fuselage components, which require explicit ID wiring per the accessibility docs. In code reviews, prefer using fuselage-forms wrappers for form fields and verify there is no unnecessary manual ID/aria wiring in files that use these wrappers. If a component uses plain fuselage components, ensure proper id wiring as per docs.

Applied to files:

  • apps/meteor/client/views/room/Header/ParentRoom/ParentDiscussion/ParentDiscussion.tsx
🔇 Additional comments (2)
apps/meteor/client/views/room/Header/ParentRoom/ParentDiscussion/ParentDiscussion.tsx (2)

2-20: LGTM!


25-26: 🎯 Functional Correctness

allowSpecialChars is already boolean
useSetting('UI_Allow_room_names_with_special_chars', false) resolves through the boolean overload, so allowSpecialChars is not boolean | undefined here and getChannelRoomName already receives a boolean.

			> Likely an incorrect or invalid review comment.

Walkthrough

Room navigation now uses router-context hooks in room views. A new useRoomRoute hook is exported, while video-conference navigation uses its local hook with tests covering channel, private group, direct message, and missing-room cases.

Changes

Room navigation migration

Layer / File(s) Summary
Room route hook and export
packages/ui-client/src/hooks/useRoomRoute.ts, packages/ui-client/src/hooks/index.ts
Adds the memoized useRoomRoute hook and exports it through the UI client hooks package.
Room view route consumers
apps/meteor/client/views/room/Header/ParentRoom/ParentDiscussion/ParentDiscussion.tsx, apps/meteor/client/views/room/body/RoomForeword/RoomForewordUsernameList.tsx
Replaces roomCoordinator navigation and link generation with router-based room routes, including federated and special-character room-name handling.
Video navigation hook localization
packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/..., packages/ui-contexts/src/index.ts
Moves useGoToRoom to a local import, updates its context imports, removes its public context export, and tests room-type-specific navigation and missing-room behavior.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels: type: chore

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly captures the main refactor: moving room navigation hooks out of roomCoordinator and ui-contexts.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)
  • ARCH-2288: Request failed with status code 401

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@tassoevan tassoevan changed the title refactor: decouple room navigation hooks from roomCoordinator and ui-contexts refactor(ui-contexts,fuselage-ui-kit,ui-client): Decouple room navigation hooks from roomCoordinator and ui-contexts Jul 22, 2026

@coderabbitai coderabbitai Bot 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.

🧹 Nitpick comments (1)
packages/ui-client/src/hooks/useRoomRoute.ts (1)

11-14: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Remove the implementation comment.

As per coding guidelines, “Avoid code comments in the implementation.”

Proposed cleanup
-/**
- * Returns a function to navigate to a room using existing room data.
- * Unlike `useGoToRoom`, this doesn't make an API call - use it when you already have the room data.
- */
🤖 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 `@packages/ui-client/src/hooks/useRoomRoute.ts` around lines 11 - 14, Remove
the implementation comment above the room navigation hook while leaving the hook
and its behavior unchanged.

Source: Coding guidelines

🤖 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.

Nitpick comments:
In `@packages/ui-client/src/hooks/useRoomRoute.ts`:
- Around line 11-14: Remove the implementation comment above the room navigation
hook while leaving the hook and its behavior unchanged.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 029a3de9-1820-48a8-a6a2-a1c40a8bba0b

📥 Commits

Reviewing files that changed from the base of the PR and between 30623d9 and 1bbc968.

📒 Files selected for processing (8)
  • apps/meteor/client/views/room/Header/ParentRoom/ParentDiscussion/ParentDiscussion.tsx
  • apps/meteor/client/views/room/body/RoomForeword/RoomForewordUsernameList.tsx
  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/VideoConferenceBlock.tsx
  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.spec.tsx
  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.ts
  • packages/ui-client/src/hooks/index.ts
  • packages/ui-client/src/hooks/useRoomRoute.ts
  • packages/ui-contexts/src/index.ts
💤 Files with no reviewable changes (1)
  • packages/ui-contexts/src/index.ts
📜 Review details
⏰ Context from checks skipped due to timeout. (5)
  • GitHub Check: cubic · AI code reviewer
  • GitHub Check: 📦 Build Packages
  • GitHub Check: Hacktron Security Check
  • GitHub Check: CodeQL-Build
  • GitHub Check: CodeQL-Build
🧰 Additional context used
📓 Path-based instructions (1)
**/*.{ts,tsx,js}

📄 CodeRabbit inference engine (.cursor/rules/playwright.mdc)

**/*.{ts,tsx,js}: Write concise, technical TypeScript/JavaScript with accurate typing in Playwright tests
Avoid code comments in the implementation

Files:

  • apps/meteor/client/views/room/body/RoomForeword/RoomForewordUsernameList.tsx
  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.ts
  • packages/ui-client/src/hooks/index.ts
  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/VideoConferenceBlock.tsx
  • apps/meteor/client/views/room/Header/ParentRoom/ParentDiscussion/ParentDiscussion.tsx
  • packages/ui-client/src/hooks/useRoomRoute.ts
  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.spec.tsx
🧠 Learnings (6)
📚 Learning: 2026-03-27T14:52:56.865Z
Learnt from: dougfabris
Repo: RocketChat/Rocket.Chat PR: 39892
File: apps/meteor/client/views/room/contextualBar/Threads/Thread.tsx:150-155
Timestamp: 2026-03-27T14:52:56.865Z
Learning: In Rocket.Chat, there are two different `ModalBackdrop` components with different prop APIs. During review, confirm the import source: (1) `rocket.chat/fuselage` `ModalBackdrop` uses `ModalBackdropProps` based on `BoxProps` (so it supports `onClick` and other Box/DOM props) and does not have an `onDismiss` prop; (2) `rocket.chat/ui-client` `ModalBackdrop` uses a narrower props interface like `{ children?: ReactNode; onDismiss?: () => void }` and handles Escape keypress and outside mouse-up, and it does not forward arbitrary DOM props such as `onClick`. Flag mismatched props (e.g., `onDismiss` passed to the fuselage component or `onClick` passed to the ui-client component) and ensure the usage matches the correct component being imported.

Applied to files:

  • apps/meteor/client/views/room/body/RoomForeword/RoomForewordUsernameList.tsx
  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/VideoConferenceBlock.tsx
  • apps/meteor/client/views/room/Header/ParentRoom/ParentDiscussion/ParentDiscussion.tsx
  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.spec.tsx
📚 Learning: 2026-05-06T12:21:44.083Z
Learnt from: juliajforesti
Repo: RocketChat/Rocket.Chat PR: 40256
File: apps/meteor/client/components/CreateDiscussion/CreateDiscussion.tsx:121-149
Timestamp: 2026-05-06T12:21:44.083Z
Learning: Field wrappers in rocket.chat/fuselage-forms (Field, FieldLabel, FieldRow, FieldError, FieldHint) auto-create htmlFor/id associations, aria-describedby, and role="alert" for errors. Do not manually set htmlFor, id, aria-describedby, or role attributes when using these wrappers. This automatic wiring does not apply to plain rocket.chat/fuselage components, which require explicit ID wiring per the accessibility docs. In code reviews, prefer using fuselage-forms wrappers for form fields and verify there is no unnecessary manual ID/aria wiring in files that use these wrappers. If a component uses plain fuselage components, ensure proper id wiring as per docs.

Applied to files:

  • apps/meteor/client/views/room/body/RoomForeword/RoomForewordUsernameList.tsx
  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.ts
  • packages/ui-client/src/hooks/index.ts
  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/VideoConferenceBlock.tsx
  • apps/meteor/client/views/room/Header/ParentRoom/ParentDiscussion/ParentDiscussion.tsx
  • packages/ui-client/src/hooks/useRoomRoute.ts
  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.spec.tsx
📚 Learning: 2026-02-26T19:25:44.063Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 38778
File: packages/ui-voip/src/providers/useMediaSession.ts:192-192
Timestamp: 2026-02-26T19:25:44.063Z
Learning: In the Rocket.Chat repository, do not reference Biome lint rules in code review feedback. Biome is not used even if biome.json exists; only reference Biome rules if there is explicit, project-wide usage documented. For TypeScript files, review lint implications without Biome guidance unless the project enables Biome rules.

Applied to files:

  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.ts
  • packages/ui-client/src/hooks/index.ts
  • packages/ui-client/src/hooks/useRoomRoute.ts
📚 Learning: 2026-02-26T19:25:44.063Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 38778
File: packages/ui-voip/src/providers/useMediaSession.ts:192-192
Timestamp: 2026-02-26T19:25:44.063Z
Learning: In this repository (RocketChat/Rocket.Chat), Biome lint rules are not used even if a biome.json exists. When reviewing TypeScript files (e.g., packages/ui-voip/src/providers/useMediaSession.ts), ensure lint suggestions do not reference Biome-specific rules. Rely on general ESLint/TypeScript lint rules and project conventions instead.

Applied to files:

  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.ts
  • packages/ui-client/src/hooks/index.ts
  • packages/ui-client/src/hooks/useRoomRoute.ts
📚 Learning: 2026-01-19T18:08:05.314Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 38169
File: packages/ui-client/src/hooks/useGoToDirectMessage.ts:20-27
Timestamp: 2026-01-19T18:08:05.314Z
Learning: Rule of Hooks: In React, hooks (including custom hooks like useGoToDirectMessage and useUserSubscriptionByName) must be called unconditionally and in the same order on every render. Do not conditionally call hooks based on values; instead, derive safe inputs if a value may be undefined (e.g., pass an empty string or undefined) and handle variations in logic outside the hook invocation. This preserves hook order and avoids violations. Apply this guideline to all files under packages/ui-client/src/hooks where hooks are used.

Applied to files:

  • packages/ui-client/src/hooks/index.ts
  • packages/ui-client/src/hooks/useRoomRoute.ts
📚 Learning: 2026-03-06T18:10:15.268Z
Learnt from: tassoevan
Repo: RocketChat/Rocket.Chat PR: 39397
File: packages/gazzodown/src/code/CodeBlock.spec.tsx:47-68
Timestamp: 2026-03-06T18:10:15.268Z
Learning: In tests (especially those using testing-library/dom/jsdom) for Rocket.Chat components, the HTML <code> element has an implicit ARIA role of 'code'. Therefore, screen.getByRole('code') or screen.findByRole('code') will locate <code> elements even without a role attribute. Do not flag findByRole('code') as invalid in reviews; prefer using the implicit role instead of adding role="code" unless necessary for accessibility.

Applied to files:

  • packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.spec.tsx
🔇 Additional comments (7)
packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.ts (1)

3-10: LGTM!

packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/VideoConferenceBlock.tsx (1)

2-2: LGTM!

Also applies to: 22-22

packages/fuselage-ui-kit/src/blocks/VideoConferenceBlock/hooks/useGoToRoom.spec.tsx (1)

1-66: LGTM!

packages/ui-client/src/hooks/useRoomRoute.ts (1)

1-9: LGTM!

Also applies to: 15-32

packages/ui-client/src/hooks/index.ts (1)

10-10: LGTM!

apps/meteor/client/views/room/Header/ParentRoom/ParentDiscussion/ParentDiscussion.tsx (1)

2-4: LGTM!

Also applies to: 14-19

apps/meteor/client/views/room/body/RoomForeword/RoomForewordUsernameList.tsx (1)

3-5: LGTM!

Also applies to: 9-18

@cubic-dev-ai cubic-dev-ai Bot 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.

All reported issues were addressed across 8 files

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread packages/ui-client/src/hooks/useRoomRoute.ts
@codecov

codecov Bot commented Jul 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.66%. Comparing base (30623d9) to head (1bbc968).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop   #41508      +/-   ##
===========================================
- Coverage    68.69%   68.66%   -0.04%     
===========================================
  Files         4134     4135       +1     
  Lines       160417   160450      +33     
  Branches     29312    29265      -47     
===========================================
- Hits        110205   110177      -28     
- Misses       45104    45159      +55     
- Partials      5108     5114       +6     
Flag Coverage Δ
unit 70.66% <100.00%> (-0.05%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

…Discussion

roomCoordinator.getRoomName prioritized fname over name only when the
room is itself a discussion or federated, and otherwise respected
UI_Allow_room_names_with_special_chars by falling back to name alone.
The router-navigation refactor collapsed this to a plain
`fname || name`, always preferring fname even when admins disabled
special chars. Replicates the original priority for channels/groups
without reintroducing the roomCoordinator dependency.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants