chat: reply to specific message

↺ Reply to...

• button [↺ Répondre/Reply]
• show replied-to-message above the message (greyed out, minimal)

added 1 deleted label

added Nice to have label

changed milestone to %0.3: Improved User Experience

changed the description

changed milestone to %0.2: Essential functions ready & corrective feedback

removed 1 deleted label

removed Nice to have label

added To do label

assigned to @bridubois

changed the description

added UX label

changed milestone to %0.2: Essential functions ready & corrective feedback

unassigned @bridubois

assigned to @DavePikopPokam

marked the checklist item possibility to reply to a comment/feedback? as completed

marked the checklist item possibility to reply to a comment/feedback? as incomplete

Thank you for working on this feature. It concerns "classic" replies to a message, and not to a comment/feedback.

Alright!

Hi Brieuc, I have some questions to help me move forward with this issue. Do you handle the reply message functionality on the backend? I mean, do you have an attribute that shows if a message is a reply or not? I couldn’t really find anything like that in the doc.

When I get a message from a session, I’d expect to see an attribute that is null by default, but if the message is a reply, it should point to the id of the replied message. Currently, I only get details like message_id, content, and created_at, but nothing about the id of the replied message

There is currently nothing, nor on the backend or the frontend for this feature. I guess we have to edit the table to add such a column, if you want to implement it that way.

Thanks, I'll wait until you've finished implementing it on the backend

I had no plan to implement it right now. Don't you want to do the backend part also? To be sure that they both match. I can help you if you have any question about it.

Sure, I can handle that part as well.

Hi @sbibauw and @bridubois,

I think this feature is completed as you can see from these images. The two users can now reply to specific messages in the chat session.

@bridubois, I encountered conflicts while merging my branch "feat/reply-to-message" with dev locally. Could we plan to resolve this together to ensure nothing gets overwritten ?

Sounds promising, thank you!

Is it normal that the arrows on the sides are not correctly connected anymore, and that the boxes are so huge?

Thanks for your feedback! The arrow is still connected, you just need to hover the mouse over the message box to see it clearly

For the size of the boxes, I'll fix it.

I was more thinking about this UI "glitch" for the arrows:

Also, does click on the "replying" scroll to the initial message? I think it would be interesting.

For sure, we can find a moment to solve the merge issue, when I'm back from Lapland!

Congrats, @DavePikopPokam. Great work.

In terms of style/visual classes, could you put it like this:

• No frame/box around "Replying to..." (simply smaller text above the message line)
• All the text (Replying to + Prev Message) in grey, small (maybe smaller than currently?), normal weight (no bold)
• Only the previous message in italics
• Truncate the previous message after ±15-20 characters (with ellipsis: ... or better: …)

Also, note that "Replying to:" should be a localized string (Replying to:/En réponse à:/...)

Ok @bridubois, I see what you meant, I'll fix the UI accordingly.

Thanks for your feedback @sbibauw, I'll fix it.

changed the description

@sbibauw @bridubois, I made a short video to show the improvements based on your feedback. Let me know if there's anything else to improve. Screen_Recording_2024-11-29_at_15.50.57

Great! I like the greyed-out text and the auto truncation. Two small additional details. Could you:

• Make the "Replying to: xxx" text even smaller?
• When replying (writing in the input field), could you put the "Replying to : xxxx" message above the input field? I.e., the input field should not move, just receive a small (again: text size and line height should be very small, white and grey, to be discrete) additional line above it.

Is this closer to what you were looking for?

Yes, that's perfect! Thanks!

Hi @bridubois, let me know when you're available so we can merge this with the dev branch maybe in peer programming. Then, I'll start working on another issue using the latest version.

Perfect, I just send you a message on Teams. Could you already create the MR, so we can see the conflicts?

When creating an MR, it seems like my current branch is outdated since nov 3, even though my last commit was made yesterday (nov 30). I think it might be a pipeline issue, but idk how to resolve it.

mentioned in merge request !10 (merged)

closed