glb_adm/f7_talk
1
0
Fork 0
Code Issues Pull Requests Actions 9 Packages Projects Releases Wiki Activity

UPSTREAM BASELINE: nextcloud/spreed v22.0.12 (без изменений)
Type checking / changes (push) Has been cancelled
Details
Type checking / test (push) Has been cancelled
Details
Type checking / typescript-summary (push) Has been cancelled
Details
Node tests / changes (push) Has been cancelled
Details
Node tests / test (push) Has been cancelled
Details
Node tests / test-summary (push) Has been cancelled
Details

Browse Source 
Источник: https://github.com/nextcloud/spreed/archive/refs/tags/v22.0.12.tar.gz
С этого коммита ветка официального Nextcloud Talk отрезана (решение владельца 2026-07-06).
Все дальнейшие изменения — только наши; версии релизов: 22.0.12-f7.N.
This commit is contained in:
glb_adm
2026-07-06 14:07:50 +00:00
commit 01acfa3b40
1716 changed files with 613013 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/integration/features/chat-3/reference-id.feature
+36
View File
@@ -0,0 +1,36 @@
Feature: chat-2/reference-id
Background:
Given user "participant1" exists
Scenario: user can send a message with a reference id and see it afterwards
Given user "participant1" creates room "group room" (v4)
| roomType | 2 |
| roomName | room |
When user "participant1" sends message "Message 1" with reference id "ref 1" to room "group room" with 201
When user "participant1" sends message "Message 2" with reference id "ref 2" to room "group room" with 201
Then user "participant1" sees the following messages in room "group room" with 200
| room | actorType | actorId | actorDisplayName | message | messageParameters | referenceId |
| group room | users | participant1 | participant1-displayname | Message 2 | [] | ref 2 |
| group room | users | participant1 | participant1-displayname | Message 1 | [] | ref 1 |
Scenario: user can send a message with the same reference id
Given user "participant1" creates room "group room" (v4)
| roomType | 2 |
| roomName | room |
When user "participant1" sends message "Message 1" with reference id "ref 1" to room "group room" with 201
When user "participant1" sends message "Message 2" with reference id "ref 1" to room "group room" with 201
Then user "participant1" sees the following messages in room "group room" with 200
| room | actorType | actorId | actorDisplayName | message | messageParameters | referenceId |
| group room | users | participant1 | participant1-displayname | Message 2 | [] | ref 1 |
| group room | users | participant1 | participant1-displayname | Message 1 | [] | ref 1 |
Scenario: too long references dont break the api
Given user "participant1" creates room "group room" (v4)
| roomType | 2 |
| roomName | room |
When user "participant1" sends message "Message 1" with reference id "f0a1611b73992b57a8533c7f618bbd145b17ef62238ece5bda548f47c76c02b2" to room "group room" with 201
When user "participant1" sends message "Message 2" with reference id "too long ref is cut off f0a1611b73992b57a8533c7f618bbd145b17ef62238ece5bda548f47c76c02b2" to room "group room" with 201
Then user "participant1" sees the following messages in room "group room" with 200
| room | actorType | actorId | actorDisplayName | message | messageParameters | referenceId |
| group room | users | participant1 | participant1-displayname | Message 2 | [] | too long ref is cut off f0a1611b73992b57a8533c7f618bbd145b17ef62 |
| group room | users | participant1 | participant1-displayname | Message 1 | [] | f0a1611b73992b57a8533c7f618bbd145b17ef62238ece5bda548f47c76c02b2 |