Add user mentions feature

[luka-nextcloud]

Signed-off-by: Luka Trovic [email protected]

• Resolves: Mention users #92
• Target version: master

Summary

It should be possible to mention users.

ToDo

• Frontend: Make sure to properly display and insert the display name
• Backend: Use proper autocompletion API Add user mentions feature #2748 (comment)
• Backend: Fix php cs @luka-nextcloud
• Frontend: Fix es lint errors @luka-nextcloud
• Backend: Emit notification to the users @juliushaertl

Follow up tickets

• Mentions for public guest names
• Highlight own user id in menu bubbles
• Pass context to notification (e.g. current line or sentence)
• On clicking the navigation, jump to the mention directly

Dependencies added (in case needed during rebase):

npm install --save @quartzy/markdown-it-mentions @tiptap/extension-mention

[susnux]

From a user perspective:

If this is about the markdown file, I would expect everything I type to be saved in the markdown file.
E.g. if I write meeting minutes and mention users (for example assign a task) I want that user to be informed so they get remembered but I also do not want a hole in the minutes.

@John volunteered to take the night shift

Or maybe with linking like

[@John](/u/johns_username) volunteered to take the night shift

[juliusknorr]

I wanted to know if we need to put the @mention in the registered file?

Yes, it should be put into the file. As mentioned we need to store the user id, but would also want the user display name as a readable representation so I tend to use the format that https://github.com/quartzy/markdown-it-mentions#quartzymarkdown-it-mentions parses already: @[Freddie Mercury](mention://user/48249279)

Notifications would be a second step then, which we could however handle in the backend when the file is actually saved.

[juliusknorr]

Regarding the UI, we should stick to how Talk and comments do it. See https://nextcloud-vue-components.netlify.app/#/Components/RichContenteditable for a reference on the UI, we cannot reuse that component however.

[juliusknorr]

Looks very nice on the UI already, I've left some comments inline.

[juliusknorr]

As a next step we may want to discuss how we issue notifications to the mentioned users. I'd say the best might be to do this on the save of the document (which might be a bit delayed), but then we can easily parse the full content and ensure that only notifications which are present are still active.

[juliusknorr]

@luka-nextcloud Pushed a few commits split by what they do when working on using the vue component for rendering. Let's move this to a mergeable state tomorrow. Missing points would be:

Moved to top post.

[luka-nextcloud]

@juliushaertl With the integration of the VueNodeViewRenderer, it seems that the content can not be rendered once we read the file after saving it. Do you have any idea why is behaving like that?

[luka-nextcloud]

@juliushaertl Updates here:
https://user-images.githubusercontent.com/89908051/186239301-97db6a34-2d50-491e-9d47-1bbc96961ebd.mov

[juliusknorr]

/compile

[max-nextcloud]

whoohoo... so cool this landed!