Unexpected behavior when giving two /by specifiers in add-task command

[Mnsd05]

When I give two /by specifiers, I would expect the name of the task to include the first /by specifier but it seems the program starts taking time from the first /by. Maybe the developers can specify in the UG or ban the use of "/"

[nus-se-script]

Team's Response

Tester description is vague and screenshot is unrelated to this bug, but bug is valid.

Multiple instances of the /by command delimiter will cause the program to reject the input, similar to Issue #2659.

The 'Original' Bug

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

Can't use words with "/by" inside task names

Steps to replicate:

• command: "clean dogs named bit/byte /by 05-05-2023"
• expected result: the task is added with typed date
• actual result: 'Please enter a valid command!'

---

_{[original: nus-cs2113-AY2223S2/pe-interim#2506] [original labels: type.FunctionalityBug severity.Low]}

Their Response to the 'Original' Bug

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

User behaviour is incorrect as the add-task command is missing from the user input and DATE is wrongly formatted.

Bug is still valid, "bit/byte" contains /by command delimiter, which causes the program to reject the command.

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]

---