refactor: rely on delete message response enrichment of deleted-for-me message in LLC

Author: MartinCupela

src/components/Message/hooks/__tests__/useDeleteHandler.test.js

@@ -81,18 +81,6 @@ describe('useDeleteHandler custom hook', () => {
     expect(deleteMessage).toHaveBeenCalledWith(message, deleteMessageOptions);
   });
 
-  it('should enrich the message in the delete response with deleted_for_me and type="deleted"', async () => {
-    jest.spyOn(client, 'deleteMessage').mockResolvedValueOnce({ message: testMessage });
-    const deleteMessageOptions = { deleteForMe: true, hard: false };
-    const handleDelete = await renderUseDeleteHandler(testMessage);
-    await handleDelete(mouseEventMock, deleteMessageOptions);
-    expect(updateMessage).toHaveBeenCalledWith({
-      ...testMessage,
-      deleted_for_me: true,
-      type: 'deleted',
-    });
-  });
-
   it('should update the message with the result of deletion', async () => {
     const deleteMessageResponse = generateMessage();
     deleteMessage.mockImplementationOnce(() => Promise.resolve(deleteMessageResponse));

src/components/Message/hooks/useDeleteHandler.ts

@@ -30,12 +30,6 @@ export const useDeleteHandler = (
 
     try {
       const deletedMessage = await deleteMessage(message, options);
-      // necessary to populate the below values as the server does not return the message in the response as deleted
-      if (options?.deleteForMe) {
-        // deleted_at is not available for messages that are deleted_for_me
-        deletedMessage.deleted_for_me = true;
-        deletedMessage.type = 'deleted';
-      }
       updateMessage(deletedMessage);
     } catch (e) {
       const errorMessage =