This allows to set the sections of an artidoc document. Payload looks like the following: ``` { "sections": [ {"artifact": { "id": 324845}}, {"artifact": { "id": 324844}} ] } ``` The new section order follows the submitted order (in this example: `[324845, 324844]`) With the following payload, the document becomes empty: ``` { "sections": [] } ``` If one of the artifact is not readable by the current user, then the update is rejected. This includes also its title and description since user cannot read such document. If user does not have write permissions on the document, then the update is rejected. Implementation note: The payload is not a simple array of ids, because we don't know yet if they will contain other things than artifacts (free text for example). So in order to limit the BC of the route we have to indicate that the id we are refering to is an artifact (this follows the GET counterpart by the way). We don't have any possibility to create an artidoc document, so this is not tested yet. REST tests will come in a dedicated contribution. (Took the opportunity to fix psalm issue in ArtidocRetriever and RawSectionsToRepresentationTransformer) Part of story #37542: display a read only Document Change-Id: I0744d4da56db41275a2123e421fc1762bc308c65

+621 −25

Author

Nicolas Terray (nterray) 2024-04-22 16:22

Committer

Nicolas Terray (nterray) 2024-04-24 08:09

Hash 25da9d7a2f660a86e9edfec3fa80b46851213bfe

Parent 13a4da997fcc775ed0398a91a94ec50af2ad68ce

Reference git #tuleap/stable/25da9d7a2f660a86e9edfec3fa80b46851213bfe