Rich workspaces is only provided for current folder
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
- create /rw/content and add rich workspace content
- query /rw/ and do not see workspace text for /rw/content
This results in a strange Android behaviour:
- go to /rw/
- go to /rw/content -> Android syncs for first time, thus gets workspace content
- go up to /rw/ -> syncs again, but overwrites now workspace for /rw/content/
- go to /rw/content/ again -> eTag did not changed, thus no update, thus no workspace
--> workspace content needs to be given for all folders (performance wise this should be ok, as this is an optional webdav parameter)
--> eTag must change upon workspace change (I guess this is already the case as readme.md is modified)
@juliushaertl as you implemented this, if I remember correclty
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the WebDAV requests for /rw/ and /rw/content described in the issue, comparing the rich workspace content and eTag returned for each folder. Trace the rich workspace response entry point in the repository and verify that parent-folder queries include descendant workspace content and that the eTag changes when workspace content changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript
- Domain
- api, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100