Open jing-xiang opened 5 months ago
This is intended behavior as the regular expression commands only considers integers without any letters for inputs. Hence 1e309 is not considered as an integer of 1 x 10^309 and it should not be.
Large number exception is handled gracefully as shown in the screenshot below
Team chose [response.Rejected
]
Reason for disagreement: I disagree that this bug be rejected.
No response was provided for the "/c" part being left out in the print statement during the incorrect format error message.
Also, being an intended behavior does not disqualify it as a bug. It should be "incorrect input" instead of "incorrect format" as the format that I had entered is correct.
Having said that, I think this may be a VeryLow severity issue
Expected: correct error message should be shown to reflect how that it is the number input Actual: general error message was shown. also the /c (optional) was left out for this particular error message which can confuse users