-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
feat(Mappers): add booleanMapper into mappers #54
feat(Mappers): add booleanMapper into mappers #54
Conversation
Codecov Report
@@ Coverage Diff @@
## master #54 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 25 25
Lines 366 361 -5
Branches 5 5
=========================================
- Hits 366 361 -5
Continue to review full report at Codecov.
|
3c804ec
to
6149dc3
Compare
…ise after valid number
@Siemienik what you think about create a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for great contribution 👍
I have only one comment for you, could I please you to use .parseFloat
instead of removeTextAfterValidNumber
src/mappers/booleanMapper.ts
Outdated
@@ -0,0 +1,7 @@ | |||
import { ValueMapper } from '../abstracts/ValueMapper'; | |||
|
|||
const removeTextAfterValidNumber = (value: string): string | undefined => |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Siemienik what you think about create a
utils
/helpers
folder ? problablyremoveTextAfterValidNumber
will be used in #46 and #48
This util is redundant if you use Number.parseFloat
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aah okay, i had no idea that parseFloat
already do that under the hood
It isn't required if I merge PR into master and I will do it soon after resolving: #54 (comment) |
…parseFloat instead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thank you for a contributions :)
* Upgrade deps, Upgrade exceljs to 4+ * Remove supporting for node 8&9
#53
When accepted, if so, can please label this PR with hacktoberfest-accepted 😄 ?