soc-se-bot
commented
10 months ago Team's Response
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 response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** I agree with dev team it's perhaps not in their current scope to sufficiently parse. However, since that tag was chosen, I think the severity would be still low? Considering how many inputs in their add commands exist such as tags, durations, steps, ingredients etc, even with an efficient, skilled typist, spacing errors like this might accidentally occur. While it dose not really affect normal operations, I don't think this is purely cosmetic, since it does delay the user by throwing invalid format. Thus, if it were to be something that is a valid bug to be implemented in future versions, I think it should be low severity?
Unable to detect command correctly if 1 space before / is included. Parser could handle this better?