fix: UserAutoCompleteMultiple not considering UI_Use_Real_name setting#38299
fix: UserAutoCompleteMultiple not considering UI_Use_Real_name setting#38299kodiakhq[bot] merged 3 commits intodevelopfrom
UserAutoCompleteMultiple not considering UI_Use_Real_name setting#38299Conversation
|
WalkthroughThis PR updates UserAutoComplete components to respect the UI_Use_Real_Name setting by implementing display logic that shows user real names when enabled, with usernames displayed inline for non-federated users. Changes span the option display component, avatar chip component, and includes a test case validating the new functionality. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
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. Comment |
|
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #38299 +/- ##
===========================================
- Coverage 70.40% 70.37% -0.04%
===========================================
Files 3161 3161
Lines 110639 110653 +14
Branches 19870 20091 +221
===========================================
- Hits 77895 77870 -25
- Misses 30717 30754 +37
- Partials 2027 2029 +2
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In
`@apps/meteor/client/components/UserAutoCompleteMultiple/UserAutoCompleteMultipleOption.tsx`:
- Around line 18-39: Compute a plain-text label that matches the rendered option
and use it for aria-label: create a labelText (e.g., in the same scope as
useMemo) that follows the same logic as optionLabel (if !useRealName || !name ->
username; otherwise -> `${name} (${username})`) and account for _federated the
same way optionLabel does, then replace aria-label={username} with
aria-label={labelText}. Ensure you reference useRealName, name, username,
_federated and optionLabel logic so the screen-reader text exactly matches the
visible label.
Proposed changes (including videos or screenshots)
Currently the component isn't considering the setting so having it enabled or disabled doesn't have any impact in the component. It aims to change it properly based on the setting.
The screenshots below displays how it works with the setting enabled and disabled:
Enabled
Disabled
Issue(s)
Steps to test or reproduce
Further comments
CORE-1780
Summary by CodeRabbit
New Features
Tests