[FEATURE REQUEST] New permission level in public link
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 251
- Forks
- 142
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 3
Description
Public links actually support three levels of permissions, but server is able to handle four levels:
| App | Server |
|---|---|
 |
 |
Also wording changes a little:
Current (App):
Download / View / Upload permission -> 15 (read, update, create, delete)
Expected (web):
Download / View / Edit permission -> 15 (read, update, create, delete)
Download / View / Upload permission -> 5 (create, read)
This feature is available from 10.2 version of the server. Current behaviour must stay if server is older than such version.
TASKS
- Research (if needed)
- Create branch feature/feature_name
- Development tasks
- Implement whatever
- ...
- Code review and apply changes requested
- Design test plan
- QA
- Merge branch feature/feature_name into master
PR
- App
- Library (if needed)
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
Start by tracing how the iOS app represents public-link permission levels and how it detects the server version. Compare the four server-supported levels, add the distinct Edit and Upload behavior for server version 10.2 and newer, and preserve the current behavior for older servers; done means the labels and permission values match the request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- authorization, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100