URL - path | resourceId fallback

[exalate-issue-sync]

Description

User Stories

• As a user who keeps bookmarks in the browser, I'd like to bookmark the files I often work with, so that I can access them quickly. I want the bookmarks to still work, even when I change the folder name or move a folder to another location.

• As a user I would like to be able to copy the URL and give it to a colleague, so that it's easier to collaborate quickly (side note: requires respective permissions to the resource e.g. via a group share or similar, and the resource id in the URL).

Value

• The URL can be bookmarked
• The bookmarked URLs remain stable even if the path changes

Acceptance Criteria

• resource ids have the format base64(<storage_id>:<file_id>)
• resource loading:
  • path takes precedence over the id, but requires validation if both are given. workflow:
  • 1: try to load resources by path
  • 2: if loading by path fails:
    • if id present: load by id + rewrites (not redirect because the operation shouldnt be in browser history) to URL with correct path and id
    • if id absent: show "resource not found" page
  • 3: if loading by path succeeds:
    • if id present: must match with propfind response, otherwise "resource not found" page
    • if id absent: render result and rewrites (not redirect because the operation shouldnt be in browser history) to URL with correct path and id
• whether or not the URL contains an id as query param must be configurable (client side config, since it's not relevant for other client platforms), if the feature is disable none of above points take place

Definition of done

• Functional requirements
  [ ] functionality described in the user story works
  [ ] acceptance criteria are fulfilled
• Quality
  [ ] code review happened
  [ ] CI is green
  [ ] critical code received unit tests by the developer
  [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
• Non-functional requirements
  [ ] no sonar cloud issues

[kulmann]

There's this reva edge PR for bringing support for a propfind to the /dav/meta/<resourceid> endpoint in order to get the relative path: cs3org/reva#2741 - and that's a prerequisite for this ticket.

[kulmann]

Currently blocked by owncloud/ocis#4727