UdhayaShan1 / pe

0 stars 0 forks source link

Duplicate name condition not explained well, allow `Alex` and `ALEX` as different but not `ALEX` and `ALEX` #12

Open UdhayaShan1 opened 2 months ago

UdhayaShan1 commented 2 months ago

While I understand

image.png

I believe this should at least be well explained as to why we allow this yet in the name of flexibility we don't allow the same capitalization (which is planned to be added as enhancement). As a user I can easily circumvent the current duplication requirement by just changing the caps of a character.

soc-se-bot commented 2 months ago

Team's Response

Hi it is under our planned enhancement that we will be accepting duplicated names in the future to provide more flexibility. image.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Testers missed the point of the issue, I am not asking about why they allow same duplicates. I am asking why different caps can be added but same caps is only considered duplicates. Different caps names should not be considered different, names should clearly be case insensitive anyways.

I have already mentioned that "we don't allow the same capitalization (which is planned to be added as enhancement)" which the developers said again.

What I am trying to flag out is why do we allow different capitalized names Bob and BOB can be input but BOB and BOB cannot be added. Users if they wish to add duplicate names can simply circumvent the duplicate check by using different capitalization. I believe this a FeatureFlaw as Bob and BOB should be considered duplicates as their enhancement said 'The current system does not allow duplicate names`.

I am confused as to why this system allows for such different caps to be added which is not justified by UG and devs in their response.

I believe this is not a rejection as there is a confusing underlying issue not addressed.