Comment mention autosuggestion

[Kyuuu]

Is your feature request related to a problem? Please describe.
When mentioning someone in the comments section it would be helpful to be able to type and select them using a handle, similar to the system used in Discord.

Describe the solution you'd like

Describe alternatives you've considered
//

Additional context
//

[JanStevcik]

Hi, can I do this issue?

[nijel]

Yes, you're welcome to do that.

[rhofer]

When mentioning someone in the comments section it would be helpful to be able to type and select them using a handle, similar to the system used in Discord.

... or similar to github or gitlab when mentioning somebody in e.g. this issue here.

Especially, when social authentication is activated (e.g. via auth0), and e.g. two users are registering with the same first name, this results into:

• USERNAME 1: Martin
• USERNAME 2: Martina31bb7cecc0b442c

In the second case, there is no chance to remember the user name, hence autosuggestion is kind of a must.

[nijel]

@SaptakS When touching the editor, please keep in mind that we want more features there in future.

Related issues I've remembered now:

• Highlighting variables and tags in the target section #3504 - placeables support
• Visual aide of doublespace in edited string #1930 - whitespace highlighting
• weblate & icu format #2856 (comment) - ICU messageformat editor, something similar will be needed for Fluent as well (Add support for Fluent (l20n) #1926)
• Make character limit less restrictive #3662 - user friendlier character limit

[nijel]

This could probably use the /api/users/. It should be exteded to support this use case. The django_filters can be added to add filtering and add support for making the API call by non superusers by filtering the available fields to them (probably just username and full_name should be exposed in this case).

[github-actions]

Thank you for your report, the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, consider supporting Weblate by donating.