Delete recipe: Ingredient name after tag not recognised if there is spacing before

[NaychiMin]

Deleting a recipe does not work if there is a space between the tag and the index/name after the tag.

[soc-se-bot]

Team's Response

Format is indeed incorrect and thus error message was returned. Same issue as master bug, solving master bug will solve this bug

The 'Original' Bug

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

Empty spaces are not sufficinetly parsed

Unable to detect command correctly if 1 space before / is included. Parser could handle this better?

---

_{[original: nus-cs2113-AY2324S1/pe-interim#490] [original labels: severity.Low type.FeatureFlaw]}

Their Response to the 'Original' Bug

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

Format is indeed incorrect and thus error message was returned. As there are different classes that uses add, we decided to implement several valid flags for recipes r/, ingredients i/, and shortcuts sc/. As sc / is an invalid flag, hence it will not detect the command.

We understand what tester means, but it is a very low priority feature, which most users will never face if they follow help commands or refer to UG/DG

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)

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

## :question: Issue response Team chose [`response.NotInScope`] - [x] I disagree **Reason for disagreement:** > Format is indeed incorrect and thus error message was returned. The command 'delete r/ 1' is not considered invalid as the user is following the user guide by keying in delete r/RECIPE_ID and from the user's point of view, they do not see it as Id = " 1" and instead sees it as Id=1 which indeed is a valid and existing dish ID. Additionally, the UG did not specify this as 'not supported' or 'coming in the future version' as they should have if it was to be considered as 'response.NotInScope' as shown below.  Hence, this should be considered as a valid bug.

---

## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [x] I disagree **Reason for disagreement:** This is a functionality bug as its behaviour differs from normal expectations. The expected output would have been to delete the respective dish.  The following bugs would be considered feature flaw: 

---

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** Only cosmetic bugs should be marked as very low as shown below. This is not a cosmetic bug.  However, after thinking of it without the stress of PE, I realised that it should be of type 'severity.Low' and not 'severity.Medium' :)

---