Open bhnuka opened 10 months ago
Thank you for your bug report.
We have identified this report as a duplicate of a previous bug report.
In addition, this behaviour does not cause any error to the user and is unlikely to affect the normal operations of the product.
Hence, we will downgrade this to a Low severity, which is the same level as the original bug.
We hope that you understand our decision. Thank you.
[The team marked this bug as a duplicate of the following bug]
Findperson / tag / task should also follow restrictions placed on addperson/tag/task
The restriction placed on names,tags and tasks are that only alphanumeric characters are allowed
ap n/. p/93843333 e/test@gmail.com a/Test addy
However, if we do
ft .
orfp .
orftag .
, the command goes through and shows nothing (since we have no names or tags or tasks with .)
I feel like putting in non-alphanumeric characters when finding should result in an error message, which would be the same error message as the specific field eg.
fp .
should show the error shown in the first screenshot and not go through
[original: nus-cs2103-AY2324S1/pe-interim#4230] [original labels: severity.Low type.FeatureFlaw]
[This is the team's response to the above 'original' bug]
Bug #4961
Thank you for your bug report.
For
findPerson
, we have a planned enhancement in the Developer Guide to allow non-alphanumeric characters in Person's names.To be consistent with this planned enhancement, all other
find
commands will follow the format offindPerson
(i.e. accept non-alphanumeric characters) so that the user does not need to remember which find command accepts non-alphanumeric characters and which do not. This makes the user experience more smooth and intuitive.For
findTask
, currently, a task's title and note can already contain non-alphanumeric characters, so the suggestion is invalid.We hope that you understand our decision. Thank you.
- Response: Not In Scope (planned enhancement)
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: [replace this with your explanation]
findPerson can take in @, even though name can only have alphanumeric characters and spaces.