search

nus-cs2103-AY2122S1 / pe-dev-response

0 stars 0 forks source link

Not mentioned that whitespaces in between command arguments will be ignored in UG #1431

Open nus-pe-bot opened 2 years ago

nus-pe-bot commented 2 years ago

Reproduce:

  1. tag -a 1 t/pool

Works well even though based on the UG, even though the format does not match the one in the UG. User is not informed that whitespaces are ignored and find the UG misleading as it does not mention anything about whitespaces in commands in general. Similar issue also existed when editing names with trailing whitespaces.

image.png

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

jiayi1129 commented 2 years ago

Team's Response

The User Guide only tells you how we intended the features to be used, but we offer the freedom with these white spaces such that we help the users avoid errors like trailing white spaces in names and other fields which are not intended. In the case of tags, white spaces do not change the meaning of the individual words represented by the tags, thus the white spaces at the end can be safely ignored.

Duplicate status (if any):

--