Open wjayee opened 11 months ago
Thank you for your suggestion. However, in our current implementation, the UniqueMusicianList
is a crucial class that enforces uniqueness of musician names and forms the crux of many other functions in BandConnect.
While this unlikely scenario is possible to happen, it should not cause much inconvenience to users. Furthermore, allowing duplicate names will result in many other implementation issues that are beyond the scope of v1.4
.
In the meantime, one could still circumvent this problem by inputting differentiators such as John Doe Piano
and John Doe Violin
, which will be treated as two distinct names.
We hope you understand our decision to classify this issue as NotInScope
. Please let us know if you have any further queries.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
It is possible that 2 separate people have the same name, so it may not be good to check for duplicates using name