mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #2741] [bug]: Identical (Non-Unique) collection names are allowed #889
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#889
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Pranav-yadav on GitHub (Oct 5, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2741
Is there an existing issue for this?
Current behavior
When you create a new collection in under the API tabs (REST/GraphQL/Realtime), app's current logic doesn't checks if the same collection already exists.
As devs/testers/humans usually tend to use the similar names often, which could cause lot of confusions later, when they need to find the exact collection in hurry or while in HotFix mode :)
Find the attached ss if needed...
PS: You can assign this bug to me once confirmed, I'll try to fix it as part of #hacktoberfest22 as well as just because I like everything open source :)
Screenshot
Steps to reproduce
Environment
Production
Version
Cloud
@AlexHRodrii commented on GitHub (Oct 8, 2022):
Can I work on this issue?
Thanks in advance
@liyasthomas commented on GitHub (Oct 11, 2022):
Restricting users from creating collections with the same name is not a feature addition.
Since our current users might've created collections with similar names before, introducing this restriction for new users will be an anti-pattern. For those who think having duplicated collection names is an issue, they can always rename the duplicated collections to something unique. And for those who'd like to have duplicated collection names, we should keep this UX for now.