Open philip1304 opened 1 week ago
[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Thank you for spotting the error. A clarification that '/' is not allowed within the meal name should have been included with the documentation.
[The team marked this bug as a duplicate of the following bug]
"save meal" does not handle special characters in string
I suppose that the meal menu should only contain upper case or lower case alphabetical characters from "a" to "z". A wrong string format exception should be thrown And the string after "/" in the meal string is not handled in this case
save meal mat-cha /c800 _____________________________________________________________________________ Added to options: mat-cha with 800 calories _____________________________________________________________________________ save meal hot/dog /c1000 _____________________________________________________________________________ Added to options: hot with 1000 calories _____________________________________________________________________________
[original: nus-cs2113-AY2425S1/pe-interim#152] [original labels: severity.Medium type.FunctionalityBug]
[This is the team's response to the above 'original' bug]
Thank you for spotting the bug. We should have specified a constraint on meal names not having '/' inside of them. However, as this bug does not cause the programme to break, and is a rare occurrence, we have thus reclassified it to 'low'.
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 reason]
When adding a meal entry using the
add mealEntry
command and including a/
in the input, the program will ignore everything between the first/
and the/c
input.Steps to reproduce:
add mealEntry
command. E.g.,add mealEntry grapes w/ juice /c200
/
and the/c1
grapes w with 200 calories