You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Items for the Tester to Verify
❓ Issue response
Team chose [response.NotInScope]
I disagree
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
The text was updated successfully, but these errors were encountered: