You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
- 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
- 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
- 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
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)
The text was updated successfully, but these errors were encountered: