search

trash-bin99 / pe

0 stars 0 forks source link

Duplicate folder names with different capitalisation are allowed #6

Open trash-bin99 opened 2 years ago

trash-bin99 commented 2 years ago

image.png

Steps to reproduce: Type in the 2 following commands: mkdir d and mkdir D

Expected: User running the second command should throw an error, as folder name is duplicated and it is not mentioned in the User guide the constraints regarding case sensitivity.

Actual: Both commands are executed successfully.

Case sensitivity should be kept consistent throughout to make it easier for users to know the constraints of each command. For instance, in the find contacts command, the user input is case-insensitive.

image.png

However, for this input, it is case sensitive, as previously demonstrated.

nus-pe-bot commented 2 years ago

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Folder name not specified as case-sensitive for echo command in UG

image.png

Steps to reproduce 1) Create a new folder with the name 'bruh' with command mkdir bruh

2) Run the command echo 1 >> bRUH, with at least one contact in the list.

Expected: contact 1 is added to the folder 'bruh'

Actual: Error, specified folder could not be found

[original: nus-cs2103-AY2122S1/pe-interim#3725] [original labels: severity.Low type.FeatureFlaw]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Functionality and feature works as intended - folder name is case-sensitive - but it is not stated in the UG. Hence, we re-categorized to DocumentationBug.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: I believe this issue is separate from the other issue, as this issue concerns the functionality of the method mkdir, while the original issue concerns the functionality of the method echo.

:question: Issue type

Team chose [type.DocumentationBug] Originally [type.FeatureFlaw]

Reason for disagreement: image.png

I believe that it is a feature flaw as I believe this would make the feature less useful for normal usage (e.g. when the user accidentally capitalises a letter) and it was not explicitly stated that this behaviour was intended, but I do agree that it could be argued as a documentation bug as well as it was not mentioned in the UG.