-
-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
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
Valid Number #235
Comments
We would, but need to understand first the usecases. I can imagive having const isValidNumber = R.either(RA.isFloat, RA.isInteger); In ramda-adjunct we already have |
That's a fair point. I agree. |
@Undistraction go for a PR then. @BjornMelgaard opinion ? |
no |
So is that a no to a PR? |
@Undistraction sorry, I meant I have no comments) |
@BjornMelgaard OK. Thanks. I'll go ahead. |
@Undistraction, @BjornMelgaard going for 2.2.0 release after the CI finishes the build for the last commit of this repo. I would specially like to thank @Undistraction for his contributions for this release. |
@charon Thanks. Was a pleasure. You run a pleasingly tight ship! |
@Undistraction thanks good to hear that ;] After you finish #234 and you'll still interesting in contributing further you can become commiter/contributor of this project. |
Thanks. That would be grand. |
v2.2.0 out: https://www.npmjs.com/package/ramda-adjunct |
Would you accept a PR for a Sanctary-style
isValidNumber()
?Effectively:
The text was updated successfully, but these errors were encountered: