(backend) create a dedicated endpoint to update document content

We want a dedicated endpoint to update a document content. Previously,
updating the content was made on the update action shared with all other
document's properties. When the title is updated, the response contains
the content, so a call to the s3 storage is made and we don't want this.
Isolating the content update will allow us in the next commit to remove
the content from the Document serializer.
This commit is contained in:
Manuel Raynaud
2026-04-27 15:06:34 +02:00
parent 207f21447d
commit d7a186a98b
10 changed files with 737 additions and 35 deletions
+1
View File
@@ -1309,6 +1309,7 @@ class Document(MP_Node, BaseModel):
"collaboration_auth": can_get,
"comment": can_comment,
"formatted_content": can_get,
"content_patch": can_update,
"cors_proxy": can_get,
"descendants": can_get,
"destroy": can_destroy,