-
-
Notifications
You must be signed in to change notification settings - Fork 653
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
Handle unknown users on profile and reactions-list screens #5790
Conversation
This is modeled on what we do in zulip-flutter (at ProfilePage), but omitting the icon for expedience in this legacy codebase.
The icon itself doesn't convey anything specific about "muted", and we'll use it in another case shortly.
Making this into normal statement control flow, rather than a `?:` operator, gives it more room to comfortably expand.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! One nit, then please merge at will. Merging.
let displayName; | ||
let displayEmail; | ||
if (!user) { | ||
displayName = _('(unknown user)'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a new UI string; we should add it to messages_en.json.
Ah, and I see it wasn't added to messages_en.json in this PR for the simple reason that it's already there :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. I actually did initially add it there, and then got a warning about a duplicate key :)
Since zulip#5790 last month, UserItem has been gracefully handling users we don't know about. Use that, instead of special-casing with a plain ZulipTextIntl, which we'd been doing since 2022-06 (0a10831) when CustomProfileFields was added.
Since zulip#5790 last month, UserItem has been prepared to gracefully handle users we don't know about. Use that, instead of special-casing with a plain ZulipTextIntl, which we'd been doing since 2022-06 (0a10831) when CustomProfileFields was added. The change won't be visible unless a given user object is actually absent; that'll start happening when we do zulip#5808. See screenshots: zulip#5809 (comment)
Since zulip#5790 last month, UserItem has been prepared to gracefully handle users we don't know about. Use that, instead of special-casing with a plain ZulipTextIntl, which we'd been doing since 2022-06 (0a10831) when CustomProfileFields was added. The change won't be visible unless a given user object is actually absent; that'll start happening when we do zulip#5808. See screenshots: zulip#5809 (comment)
Since zulip#5790 last month, UserItem has been prepared to gracefully handle users we don't know about. Use that, instead of special-casing with a plain ZulipTextIntl, which we'd been doing since 2022-06 (0a10831) when CustomProfileFields was added. The change won't be visible unless a given user object is actually absent; that'll start happening when we do zulip#5808. See screenshots: zulip#5809 (comment)
Since zulip#5790 last month, UserItem has been prepared to gracefully handle users we don't know about. Use that, instead of special-casing with a plain ZulipTextIntl, which we'd been doing since 2022-06 (0a10831) when CustomProfileFields was added. The change won't be visible unless a given user object is actually absent; that'll start happening when we do zulip#5808. See screenshots: zulip#5809 (comment)
This fixes the issues I found just now when investigating #5787, our compatibility with the upcoming "limited guests" feature. Specifically: