We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CWOPTS.isnum() function will consider an empty string as a valid number.
I discovered this during interactive testing. I forgot the steps to reproduce.
an empty string should be an invalid number. Function should return False.
incorrectly returns True (valid number).
The text was updated successfully, but these errors were encountered:
Issue #18 - bug fix - CWOPTS.isnum() incorrectly considered an empty …
0e3e494
…string as a valid number.
Merge pull request #19 from w7sst/18-cwoptsisnum-incorrectly-consider…
5e5fb50
…ed-an-empty-string-as-a-valid-number Issue #18 - bug fix - CWOPTS.isnum() incorrectly considered an empty string as valid
w7sst
When branches are created from issues, their pull requests are automatically linked.
Description
CWOPTS.isnum() function will consider an empty string as a valid number.
Steps To Reproduce
I discovered this during interactive testing. I forgot the steps to reproduce.
Expected behavior
an empty string should be an invalid number. Function should return False.
Actual Behavior
incorrectly returns True (valid number).
The text was updated successfully, but these errors were encountered: