Share folder As "chosen name"
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
When sharing a folder to a group or user, the share gets the name of the folder you as a sharer have this in your own folder tree.
Of course same applies to sharing a subfolder.
Though what I have is the following:
Italy
-- subfolderOne
-- subffoldeTwo
-- CONTENT
Spain
-- subfolderOne
-- sufolderTwo
-- CONTENT
Germany.. and so on.
The folders CONTENT will be shared with other users/groups.
However, what they then see is
CONTENT
CONTENT(1)
Since the folder name CONTENT is required as it is part if a naming convention in other 3rd part applications I cannot change this in my own tree.
What I would like to be able to do is name the shares as a sharer.
When adding a user/group, give the share a name under "advanced settings"
So I would be able to set the name of the shared folder for the user/groups.
Current workaround is to name the folder before, share, change back to CONTENT afterwards.
Another workaround is to share CONTENT and have the user change on their end.
Both do not allow the owner of the folder to see what was a name afterwards other than keep a note somewhere.
so it would be nice if sharer could name CONTENT to "Spain Content" and "Italy Content" and on.
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
The issue does not name files, tests, or entry points. Start by tracing folder sharing and the advanced settings flow, then determine how a sharer-provided name would be stored and displayed; done means recipients see the chosen share name while the underlying folder remains CONTENT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100