Share can't be added, if a share of a different type, but same name exists
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 284
- Forks
- 91
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 50
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github (I've searched it).
- I agree to follow Nextcloud's Code of Conduct.
What went wrong, what did you observe?
Adding a group "Users" to the shares fails if there is already a share with the identifier "Users", but of a different kind (i.e. contact group)
What did you expect, how polls should behave instead?
Adding a group with the same name of another share, but of a different type should be possible.
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 names no files, tests, or entry points. Reproduce adding the “Users” group when a same-named contact group exists, then trace the share-add path. Done means both share types can coexist under the same name and the regression is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100