pnp / pnp/sp-dev-fx-controls-react

ListItemComments - can't use @mention using display name

Open
#1,610 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted type:bug
Dominant language
TypeScript
Stars
433
Forks
418
Avg merge
5d 6m
Merged PRs (30d)
19

Description

Category

[ ] Enhancement

[X] Bug

[ ] Question

Version

Please specify what version of the library you are using: [3.15]

Expected / Desired Behavior / Question

Currently you are unable to @mention a user using their display name, as soon as you hit space it breaks the mention, instead you need to enter the users email address. This is confusing and counter-intuitive, especially as this is not how @mention works in other microsoft apps, it also requires you to know the users email address.

Observed Behavior

When trying to @mention someone you should be able to use their display name, like users are used to using in other applications.

Steps to Reproduce

This is happening in web parts and form customizers, in at least 3.14 and 3.15.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the ListItemComments control and reproduce the issue in a web part or form customizer using a user's display name. Trace what happens when a space is entered during the mention flow. Done means a display-name mention remains usable after spaces, without requiring the user's email address.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.