-
Notifications
You must be signed in to change notification settings - Fork 28
feat: Implement a custom notification message for mentions #1675
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
jancborchardt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small detail: In Collectives we never refer to a page as "Readme" so it would be good to use the page name. Meaning:
- If it's the Readme of a folder, use the folder name
- If it's the Readme of a Collective, just use only the Collective name and don't append the "- Readme" part
Is that possible @juliusknorr?
12a2994 to
9568d6e
Compare
mejo-
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @juliusknorr, works well! I pushed some minor changes (displaying "Landingpage" instead of "Readme"), a cypress test and some fixes to make psalm happy.
Signed-off-by: Julius Knorr <[email protected]>
Signed-off-by: Jonas <[email protected]>
Signed-off-by: Jonas <[email protected]>
c7d99a6 to
6f3e680
Compare
Unpacking associative arrays requires PHP 8.1+ Signed-off-by: Jonas <[email protected]>
Signed-off-by: Jonas <[email protected]>
6f3e680 to
09d7ca0
Compare
Requires nextcloud/text#6923
Fixes #1469
This makes sure that for mentions in collectives we have a proper notification message and redirect the user to the collective page instead of the file.
🏁 Checklist
npm run lint/npm run stylelint/composer run cs:check)