Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

regression: UserAvatar should always render BaseAvatar #34061

Open
wants to merge 3 commits into
base: release-7.1.0
Choose a base branch
from

Conversation

dougfabris
Copy link
Member

@dougfabris dougfabris commented Nov 26, 2024

Proposed changes (including videos or screenshots)

Introduced here: #32906

Previously we didn't check userId or username to render BaseAvatar, neither throw an Error. There are some cases that username can be undefined such as ComposerBoxPopupUser which will break the entire UI if we keep the current solution. The PR aims to always render the BaseAvatar as we were doing before, because this component has an error validation when trying to load an invalid URL, rendering a Skeleton as a fallback

Issue(s)

Steps to test or reproduce

Further comments

CORE-834

Copy link
Contributor

dionisio-bot bot commented Nov 26, 2024

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

Copy link

changeset-bot bot commented Nov 26, 2024

⚠️ No Changeset found

Latest commit: 41445d2

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

@dougfabris dougfabris added this to the 7.1.0 milestone Nov 26, 2024
Copy link
Contributor

github-actions bot commented Nov 26, 2024

PR Preview Action v1.4.8
🚀 Deployed preview to https://RocketChat.github.io/Rocket.Chat/pr-preview/pr-34061/
on branch gh-pages at 2024-11-26 19:51 UTC

Copy link

codecov bot commented Nov 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.75%. Comparing base (97edecc) to head (f934f58).

Additional details and impacted files

Impacted file tree graph

@@              Coverage Diff               @@
##           release-7.1.0   #34061   +/-   ##
==============================================
  Coverage          75.75%   75.75%           
==============================================
  Files                510      510           
  Lines              22078    22078           
  Branches            5387     5387           
==============================================
  Hits               16726    16726           
  Misses              4706     4706           
  Partials             646      646           
Flag Coverage Δ
unit 75.75% <ø> (ø)

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

@dougfabris dougfabris marked this pull request as ready for review November 26, 2024 21:00
@dougfabris dougfabris requested a review from a team as a code owner November 26, 2024 21:00
@@ -6,7 +6,7 @@ export type AvatarUrlContextValue = {
getUserPathAvatar: {
(username: string, etag?: string): string;
(params: { userId: string; etag?: string }): string;
(params: { username: string; etag?: string }): string;
(params: { username?: string; etag?: string }): string;
Copy link
Member

Choose a reason for hiding this comment

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

how is this possible? a function that accepts an empty object will return something?

Copy link
Member Author

Choose a reason for hiding this comment

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

@ggazzo did you checked the function?

Copy link
Member

Choose a reason for hiding this comment

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

sure and still makes no sense rendering something if you have no info about thats why this params are wrong

you are trying to fix a different problem with a "naive" solution

your problem is the /invite @something breaking right ?

for a small fraction the autocomplete uses one render type for a different item list thats why username is undefined there. but this is the real problema.

even this change solves the issue, I think you are covering the wrong place

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.

3 participants