-
Notifications
You must be signed in to change notification settings - Fork 32
✨ [Frontend] Conversations: Edit and Delete messages #7954
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
✨ [Frontend] Conversations: Edit and Delete messages #7954
Conversation
|
@mergify queue |
🟠 Waiting for conditions to match
|
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.
Pull Request Overview
Adds the ability for users to edit and delete their own conversation messages via UI controls and new API endpoints.
- Introduces
editMessageanddeleteMessagemethods in the Conversations client - Maps new PUT/DELETE endpoints in the Resources module
- Extends the message UI and AddMessage dialog to support edit and delete flows, refreshing the view on changes
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| services/static-webserver/client/source/class/osparc/study/Conversations.js | Added editMessage and deleteMessage client methods |
| services/static-webserver/client/source/class/osparc/data/Resources.js | Defined editMessage (PUT) and deleteMessage (DELETE) endpoints |
| services/static-webserver/client/source/class/osparc/conversation/MessageUI.js | Added menu button, handlers for edit/delete, and fire events to refresh messages |
| services/static-webserver/client/source/class/osparc/conversation/Conversation.js | Propagate studyId to messages and attach listeners for edit/delete events to refetch messages |
| services/static-webserver/client/source/class/osparc/conversation/AddMessage.js | Extended constructor and layout to support editing existing messages and fire messageEdited |
Comments suppressed due to low confidence (3)
services/static-webserver/client/source/class/osparc/conversation/AddMessage.js:39
- [nitpick] The event
commentAddedis inconsistent with the rest of the code that refers to messages; consider renaming it tomessageAddedfor clarity.
"commentAdded": "qx.event.type.Data",
services/static-webserver/client/source/class/osparc/study/Conversations.js:97
- [nitpick] Add JSDoc comments to
editMessageanddeleteMessagemethods explaining parameters and return value for consistency with other client methods.
editMessage: function(studyId, conversationId, messageId, message) {
services/static-webserver/client/source/class/osparc/study/Conversations.js:97
- Consider adding unit or integration tests for the new
editMessageanddeleteMessageclient methods to verify correct parameter mapping and error handling.
editMessage: function(studyId, conversationId, messageId, message) {
services/static-webserver/client/source/class/osparc/conversation/MessageUI.js
Outdated
Show resolved
Hide resolved
services/static-webserver/client/source/class/osparc/conversation/MessageUI.js
Show resolved
Hide resolved
services/static-webserver/client/source/class/osparc/conversation/Conversation.js
Show resolved
Hide resolved
matusdrobuliak66
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.
Idea: We can have new type "DELETE_MESSAGE" and you can have updated the type with group_id and the same as we show notification, we can show deleted message :)
|
@mergify queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 904b669 |
|
|
Please retry analysis of this Pull-Request directly on SonarQube Cloud |



What do these changes do?
Related issue/s
How to test
Dev-ops