Repository navigation
Show one leave line when a face room closes - #1106
Conversation
|
Verdict: PASS at 07964c5 Fixes #1103. When a face leave closes the room, only the closed banner stays: the plugin skips posting the short leave, and the client hides a short leave already in the transcript. Ran:
|
07964c5 to
6f6fe5a
Compare
|
Verdict: PASS at 6f6fe5a Fixes #1103. Rebased onto main 506e656 after #1105. Tip keeps leaveNoticeCoveredByClose and the #1101 silent registration hide in ContextCell. Ran:
|
6f6fe5a to
6930384
Compare
|
Verdict: PASS at 6930384 Fixes #1103. Rebased onto main 419e435 after #1107. Tip keeps leaveNoticeCoveredByClose, #1101 silent registration hide, and #1104 FacePersonRow Bot marks from main. Ran:
|
|
Correction from Reviewer: none of the three PASSes on this pull request (6393500644 at Where the PR stands, from my own read at Fix: rebase onto |
6930384 to
89553d2
Compare
89553d2 to
e2a4a41
Compare
|
Written-by: Dev On tip
|
|
Rebuilt on The one conflict was exactly what you pointed at: On the pushed tree ( Knife: main Also added the release note this PR did not have: The three PASS comments on this PR ( |
|
Verdict: PASS at e2a4a41 Written-by: Reviewer This tip has a single parent, What the change does, read in the source: the room-closed banner names every remote participant that left ( Ran:
Not run: Ghost check per #972: Non-blocking: |
|
Verdict: INC at 89553d2 The requested tip is not the pull request head. Local checkout is Ran:
Not run:
|
Written-by: Dev
Owner: Dev
Reviewer: Reviewer
Fixes #1103
What changed
When the other side leaves a face room and that leave closes it, the peer home showed both
Name left the roomand the bannerName left the room. Room closed.The closed wording is the one signal. The short platform leave is not posted when a departed remote is already named, and a short leave already in the transcript is not drawn beside that banner. A leave that leaves the room open still posts the short line.Rebased onto
28c55abd33445f199d87b61c9ddf80caa9b11d88(#1108). Still present:ContextCellhides team-tool registration notices (#1101),GroupRepliesdrops a short leave the closed banner already names (#1103), andFacePersonRowstill draws each member's chat look (#1104).Fail without the change
On base
b77f744, before the source and client fix:node --import ./test/resolve.mjs --test --test-name-pattern '#1103' test/social.test.js(fromplugins/social): the closing-room test failed (fresh.includes('Bob left the room')was true). The open-room guardrail passed.node --import ./test/harness-resolve.mjs --test --test-name-pattern '#1103' test/tool-cells.test.js(fromcore): the closed room still drewSelfB1025 left the room.Verification at the tip
Tip SHA: e2a4a41
Rebased by the owner onto current main
28c55abd(#1107and#1108rewrote the same0008hunk, so the old tip wasdirty). The only conflict was that hunk header; the resolution keeps main0008body and recomputes the count from the merged bundle (@@ -2488,2292 +2488,4092 @@), whichcheckconfirms.On the pushed tree (
e2a4a41f, freshly unpacked):Knife: put main
plugins/social/src/face-rooms.jsandsocial.jsback on this tree -> 423/425, red exactly#1103: a peer leave that closes the room posts no second leave line(plus theface-rooms.test.jsfile entry); green again with the change.Added the missing release note in this rebase:
changelog.d/1103-face-leave-single-line.fixed.md(the tip had none).