Open nidhi-nayak opened 6 months 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 the suggestion and we will definitely make sure to take this into account as an additional point in the UG. However, given that in the UG, the command stated is get expenses insights
and not get__expenses__insights, whereby an "_" indicates a spacing. Hence, having extra spaces achieves the expected behavior of being recognized as an invalid command.
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your reason]
the get expenses command does not work with trailing spaces or additional spaces within the command. for most space sensitive commands, this is recorded in the UG. so the user would assume that this command is space insensitive.