-
Notifications
You must be signed in to change notification settings - Fork 452
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
Add checkbox for locking conversation #4331
Add checkbox for locking conversation #4331
Conversation
8f049ee
to
45f5e9e
Compare
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.
See first comment
|
bf290e3
to
9b50e33
Compare
adjusted based on review and conflict fixed |
Added logic for setting a conversation to read-only. Signed-off-by: Vincent Petry <vincent@nextcloud.com>
In a read-only conversation, the following actions are not available: - start call button is hidden - field for posting fields is hidden - reply button in the messages list is hidden Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Whenever an error occurs when sending a message, the message is now put back into the field and the temporary one is removed from the messages list. Whenever a conversation was locked or lobby was enabled concurrently, posting a message before the UI update could result in a 403 or 412 error. These now display a proper message to inform about missing permissions. Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Moved isConversationReadOnly condition on the reply action button instead of affecting all possible (future) actions. Now using `showError` instead of the global OC notification, the displayed border now has the correct color. Renamed "room" to "conversation" in the error message. Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
9b50e33
to
51debd5
Compare
|
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.
🦈
@PVince81 @nickvergessen |
For now this is not what they are designed for |
OK, can I try to implement a read only setting for !moderators? |
I need the function to lock the conversation for not moderator users. Eg as a dropdown:
@PVince81 @nickvergessen What do you think? |
Well the mobile clients would need to understand that too. So not possible for 11. We can see for 12 |
For education scenarios this feature would be very important and helpful. A moderator (teacher) should be able to write in locked chats too. So you could create chats with information for students and parents which are locked and other ones, which are used for the ongoing communication between teachters, staff, students and so on. |
Nobody can write on locked conversations. |
Added logic for setting a conversation to read-only.
Fixes #1647
Todos
Manual Tests
Automated Tests