[tammi-23]

Description

"Save As" and "Export As" (e.g. PDF) in Collabora only offered a file name input, so documents could only be saved next to the current file. Both actions now open the location picker, where the user can choose the target folder and the file name.

• UI_SaveAs opens the LocationPickerModal with chooseFileName instead of the FileNameModal. The file name is prefilled with the current name, or with the new extension when exporting.
• The chosen folder is sent to Collabora as a path relative to the folder of the current file (Action_SaveAs Filename), because WOPI PutRelativeFile resolves the target relative to that folder.
• Folders outside the current folder or its subfolders can't be reached that way, so an error message is shown and nothing is saved.
• If a file with the chosen name already exists in the target folder, a free name is picked (name (1).ext), like the file list does.
• After saving, the editor switches to the new file. The route is now built via getDriveAliasAndItem, so this also works when the file was saved into a subfolder of a received share or public link.
• The conflict check lists the target folder by its resource (path and id), so it also works in public links, where listing by id alone returns the link root.
• FileNameModal.vue is removed since it is no longer used.

Known limitation: saving into a parent folder or another space isn't possible because of how PutRelativeFile works. Lifting that would need a backend change.

Related Issue

• Fixes: no separate issue, requested internally

How Has This Been Tested?

• test environment: local OpenCloud with Collabora, Chrome
• test case 1: personal space, Save As into a subfolder → new file is created there and opened in the editor
• test case 2: personal space, export as PDF into a nested subfolder → PDF is created there
• test case 3: target folder above the current folder → error message, nothing is saved
• test case 4: received share (editor role), Save As into a subfolder with an existing file of the same name → name (1).odt is created and opened
• test case 5: received share, export as PDF into a nested subfolder → PDF is created there
• test case 6: public edit link (logged out), Save As into a subfolder, also with a name conflict → name (1).odt is created and opened
• test case 7: public edit link, export as PDF into a nested subfolder; link root as target → error message
• unit tests for useCollaboraPostMessages

[AlexAndBear]

Works great, but the known limitation (only current + subfolders) is very limiting, we should open a backend issue, since you mentioned, it's a server side restriction.

[kulmann]

Nice 💪 Could you please open a backend issue for the path limitation? 🙈