Open warrencxw opened 2 years ago
Comparing with the error message, it is clear that the problem with the timer input is with respect to TIMER_DURATION (inputting a 0 second custom timer) since 'start /custom' supplied by the user is in the correct format, following the format as stated in the error message.
Team chose [response.Rejected
]
Reason for disagreement: Indeed, it is clear that the problem with the timer is with respect to TIMER_DURATION
, that I do not disagree. The issue that is raised in the bug report itself is, and I quote,
..., but does not explain what is wrong about the input.
It does not explain what exactly is wrong with the TIMER_DURATION
provided, and does not help the user in figuring out how they can fix the input in order to get the command to work.
According to the module website, it is a feature flaw for an error message to be not specific enough.
When a custom timer is started with an input of
0
seconds as per the following command, an error message that says that the timer input is incorrect is provided, but does not explain what is wrong about the input.start /custom 0
This could especially be an issue if a typo was made and missed out a 6 in 60 for example.