Unexpected user ID shown instead of name
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Hi, apologies if this is a duplicate issue, I have looked but couldn't see anything that looked similar.
Steps to reproduce
- Create a SAML user
- Write a message to them
Expected behaviour
The message preview for a user what is sent should be consistent. E.g. when I @[person] I expect the message to show the same, rather than be replaced by their user ID.
Preview
Sent
Actual behaviour
The message is not consistent with the preview.
Talk app
Talk app version: 15.0.6
Custom Signaling server configured: yes
Custom TURN server configured: yes
Custom STUN server configured: yes
Browser
Microphone available: yes
Camera available: yes
Operating system: macOS
Browser name: Chrome
Browser version: 114
Nextcloud Version: 25.0.7 Enterprise
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the issue's reproduction steps with a SAML user in Talk 15.0.6, comparing the message preview with the sent message in Chrome. Trace the mention handling responsible for replacing @[person] with a user ID; done means the preview and sent message display the same user name. No source file or test is named, so the relevant Talk code and coverage must first be located.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- authentication, full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100