Open Zer0Legion opened 5 months ago
Thank you for the report but we chose to tag this as not in scope because rectifying it is less important (based on the value/effort considerations) than the work that has been done already and the software would not crash because of this issue.
Team chose [response.NotInScope
]
Reason for disagreement: I disagree that rectifying it is less important.
Error messages are crucial and are a part of every single feature the team has implemented. Not rectifying this means the issue will be carried on to any future add-ons the team decides to implement.
Additionally, the cost of implementing this feature, changing literally 1 variable, seems to be too small to deem it as "not in scope".
An error message is red. Against the app's (admittedly very very beautiful) background, it may be a little hard to read.
Screenshot:
Observe the command with red font in the command box.