fix(feedback): show the operator reply only on the player's latest message
CI / changes (pull_request) Successful in 2s
CI / unit (pull_request) Successful in 9s
CI / integration (pull_request) Successful in 13s
CI / ui (pull_request) Successful in 47s
CI / gate (pull_request) Successful in 0s
CI / deploy (pull_request) Successful in 1m8s

A reply was bound to 'the latest message that has a reply', so after the player
read a reply and sent a new (unanswered) message, the old reply kept showing as
'Ответ на ваше последнее сообщение'. Bind it to the single most-recent message
instead: sending any new message immediately drops the previous reply (the new
message has no reply yet), well before the one-week window. Client clears the
reply optimistically on submit; the mock mirrors it; inttest covers the case.
This commit is contained in:
Ilia Denisov
2026-06-15 12:59:18 +02:00
parent 5287794a72
commit 1ae43080ec
5 changed files with 64 additions and 14 deletions
+1
View File
@@ -418,6 +418,7 @@ export class MockGateway implements GatewayClient {
}
async feedbackSubmit(_body: string, _attachment: Uint8Array | null, _attachmentName: string, _channel: string): Promise<void> {
this.feedbackPending = true;
this.feedbackReply = null; // a new message: the previous operator reply no longer shows
}
async feedbackGet(): Promise<FeedbackState> {
this.feedbackReplyUnread = false; // fetching the screen delivers (reads) the reply
+2 -1
View File
@@ -71,7 +71,8 @@
removeFile();
sent = true;
// The message is now under review: block resending until the operator handles it.
view = { canSend: false, blockedReason: 'pending', reply: view?.reply ?? null };
// A new message has no reply yet, so the previous operator reply stops showing.
view = { canSend: false, blockedReason: 'pending', reply: null };
} catch (e) {
handleError(e);
} finally {