owncloud / owncloud/android

[FEATURE REQUEST] Sharing NG: Edit existing link

Open
#4,970 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature request Share by Public Link
Dominant language
Kotlin
Stars
4.2k
Forks
3.1k
Avg merge
1d 12h
Merged PRs (30d)
7

Description

1. Permission:

libre.graph/driveItem/permissions/update

if available, it shows the pencil icon in the rows

2. Edit Link

Same view as the create, with all the fields with the set values

  • Name (optional) -> Max 255 chars
  • Level of permission (mandatory)
  • Password (not always mandatory, depends on capabilities) -> Apply password policy
  • Expiration date (optional)
3. Submission
3.1 name, permission and expiration date:

PATCH https://<url>/graph/v1beta1/drives/<drive-id>/items/<item-id>/permissions/<link-id>

with body

{
    "link": {
        "type": "edit",
        "@libre.graph.displayName": "Tested it"
    },
    "expirationDateTime": "2026-09-27T10:36:00.000Z"
}

including only the changed fields

3.2 Password

POST https://<url>/graph/v1beta1/drives/<drive-id>/items/<item-id>/permissions/<link-id>/setPassword

with body

{
"password": "<new_pass>"
}

The button to submit with text SAVE

TASKS
  • Research (if needed)
  • Create branch feature/feature_name
  • Development tasks
    • Implement whatever
    • ...
    • Implement unit tests (if needed)
  • Code review and apply changes requested
  • Design test plan
  • QA
  • Merge branch feature/feature_name into master

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Sharing NG permission rows and the existing create-link view, then review the listed PATCH and setPassword endpoints. Done means users can edit supported link fields, apply the password policy, submit with SAVE, and cover the behavior with appropriate unit tests and QA.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
api, mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.