Open yijiano opened 1 week ago
Thank you for bringing this up. The documentation should have reflected that adding standalone flag formatted inputs is not allowed or might be problematic, since "event-p" will work but "event -p" will cause problems when adding participants. For the same reasons, this is unlikely to affect many users since it is unlikely to have such standalone flag inputs as part of an event name. As such, I have changed the bug type to be a documentation bug but kept the severity level as low.
Team chose [type.DocumentationBug
]
Originally [type.FunctionalityBug
]
Reason for disagreement: Thank you for the response. However, I would like to respectfully disagree with the change in bug type.
The restriction on standalone flags in user inputs was not specified in the UG, and hence the resulting output should have been considered as legitimate during testing. The fact that there was no indication that standalone flags were restricted in the UG does not justify the app not being able to handle such input, which was main reason for my initial report.
Moreover, here is what constitutes a documentation bug:
Thus, as the root cause of the bug was that there was insufficient handling of potentially problematic inputs, I believe that the bug type should not be changed, and should remain as a functionality bug.
Steps to recreate: