feat(conversationfolder): use per share conversation folders#17346
feat(conversationfolder): use per share conversation folders#17346miaulalala merged 2 commits intomainfrom
Conversation
9f13642 to
270f200
Compare
|
Hi |
no not for now as that is quite a heavy process (depending on the number of users). But the old folder will still be accessible and all shares will stay as is in the chat, even if the conversation is renamed. |
There was a problem hiding this comment.
Please check in the other sharing tests how to list folders and shares for users (e.g. https://github.com/nextcloud/spreed/pull/17483/changes) and add a the checks here to ensure the shares are stored with correct information for the actor and recipients
There was a problem hiding this comment.
This here is also still missing, but we can do it in a follow up as well.
649496a to
2e1f1ce
Compare
23a7a8d to
7477c1c
Compare
7477c1c to
f410dae
Compare
nickvergessen
left a comment
There was a problem hiding this comment.
Since you need to resolve fixups anyway, lets simplify the boolean logic as well.
aa43380 to
11ae154
Compare
Introduces a per-share conversation subfolder scheme for Talk
attachments. Instead of a single flat attachment folder, files are
organised as:
Talk/<ConversationName>-<token>/<DisplayName>-<uid>/
A new POST /api/v1/chat/{token}/attachment endpoint accepts a file
path already inside the caller's conversation subfolder, creates a
folder-level TYPE_ROOM share (via ConversationFolderService) to give
all room members access, and posts the file_shared chat message.
The attachment folder root is configurable per user; the feature is
toggled via the `conversation_subfolders` app config key (default on)
and advertised through the existing capabilities mechanism.
AI-assisted-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Anna Larch <anna@nextcloud.com>
…tion subfolder feature Covers ConversationFolderService (quota, share deduplication, rename-on-conflict), Share/Listener mount point resolution (flat, nested group/1-1 rooms, room-not-found fallback), SystemMessage parser for the fileId path, ChatController attachment endpoint, and the full sharing-1/conversation-folder integration suite. AI-assisted-by: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Anna Larch <anna@nextcloud.com>
11ae154 to
fab2466
Compare
☑️ Resolves
🛠️ API Checklist
🚧 Tasks
🏁 Checklist
docs/has been updated or is not required