Open paulktham opened 1 week ago
I would consider this as severity.Medium : A flaw that causes occasional inconvenience to some users, but they can continue to use the product. This is because this bug only occurs under extreme testing and should be considered under "extreme user behaviour" as it is "deliberate sabotage". Also this flaw affects very minimal users as normal event names should not be containing all these symbols.
Team chose [severity.Medium
]
Originally [severity.High
]
Reason for disagreement: Thanks for the clarification, upon looking further into this issue, I have figured out that the \
is giving the application some issues with loading the saved data. So when i add an event like testing\
the error will show again as shown below.
thus I would consider this to be not
"extreme user behaviour" as it is "deliberate sabotage".
and it does not require the input to have
all these symbols.
and adding a backslash to an event name could be a harmless mistake input by the user or the way they wanted to format things.
So this flaw can affect a large number of users. I would imagine the user spending quite sometime inputting all the events and participants and if one event were to have a backslash at a unfortunate position in the naming, all their data would be gone the next time they load the cli application, therefore I still believe that this is a high severity bug.
This input which i give the command line gives the app an error and causes it to not be able to load the previously saved file.
add -e ""Special!@#$%^&*()_+{}|:\""<>?"" -t 2024-11-16 00:00 -v here -u HIGH
And when this is in the data.txt file it just says that the file does not exist