Simplifying internal/external links flow
Open
Nobody has claimed this yet.
❄️ 2026-Winter
0. Needs triage
enhancement
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
We must discuss on how to get rid of having to different kind of share links (internal vs external). "In a nutshell", the idea is to have a single share-link schema that can deal with both the public and internal cases. We could get rid of the internal link schema and use the external link schema. Access would be granted depending on the user accessing the link.
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
No files, entry points, or tests are named. Start by mapping the existing internal and external share-link flows and their access checks; done would require an agreed single-link design covering both public and internal users.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100