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

Status Chat Input: Empty mention if name property is missing, but alias, nickname or ensName is present #8691

Closed
alexjba opened this issue Dec 8, 2022 · 0 comments · Fixed by #8986
Assignees
Labels
bug Something isn't working

Comments

@alexjba
Copy link
Contributor

alexjba commented Dec 8, 2022

This issue created based on findings when StatusChatInput was added to storybook.

When the contact does not have name, but has any of the following: "name", "nickname", "ensName", "alias", mentioning him will result in empty mention. The mention suggestions work as expected. The suggestions have logic on this and the name will be the first model item not empty in ["name", "nickname", "ensName", "alias"].

Please see the below quote:

Just a small suggestion added and.. Not sure about the scope of this task but testing it I've seen this issue with maria.eth user mention:

Screen.Recording.2022-12-07.at.11.34.19.mov

Originally posted by @noeliaSD in #8653 (review)

@caybro caybro added bug Something isn't working Chat labels Dec 8, 2022
@caybro caybro self-assigned this Jan 5, 2023
@caybro caybro moved this to In Progress in Status Desktop/Mobile Board Jan 5, 2023
caybro added a commit that referenced this issue Jan 6, 2023
- follow the order of properties that `ProfileUtils.displayName()` uses
elsewhere in the application
- prefer nickname or ensName over displayName if the user has them

Fixes: #8691
@caybro caybro linked a pull request Jan 6, 2023 that will close this issue
1 task
@caybro caybro moved this from In Progress to Code review in Status Desktop/Mobile Board Jan 6, 2023
caybro added a commit that referenced this issue Jan 7, 2023
- follow the order of properties that `ProfileUtils.displayName()` uses
elsewhere in the application
- prefer nickname or ensName over displayName if the user has them

Fixes: #8691
caybro added a commit that referenced this issue Jan 9, 2023
- follow the order of properties that `ProfileUtils.displayName()` uses
elsewhere in the application
- prefer nickname or ensName over displayName if the user has them

Fixes: #8691
@github-project-automation github-project-automation bot moved this from Code review to Done in Status Desktop/Mobile Board Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants