Closed nicolasferraro closed 6 years ago
If you wait for PR #44 to be merged in (some time within the next few days probably), there will be a nice "preprocess comment" method you can use! Yes, I think changing 20.2k to 20200 would make sense :)
Thanks for volunteering to pick up this task!
Similarly, it should be easy to add modifiers like thousand, m, b, mill, billion
and so on. This could also be a good start to adding interpretation of word numbers fifty five
and so on.
That's a great idea! Maybe once the we get the "preprocess" code in, we could create some separate stories to add those modifiers and word-numbers as well :)
@nalinbhardwaj The preprocess change was just merged in FYI, so the infrastructure should be there for you to start working on this issue
@cannawen did you mean to mention @nicoferraro96 ? Isn't this already assigned to him?
MY BAD, yes, sorry!!
@cannawen Cool, I'll start working on it later today!
Hey @nicoferraro96, we have just added a CONTRIBUTING.md doc, please check it out when you have time! Sections "Etiquette", "Work on an issue" and "Make a PR" are most important
i.e. 50k miles should be processed to 50000 miles
A quick solution for this would be to add k matching to the number_regex so when we are parsing
50k
we match50k
instead of50
like we do currently. We could then either replace thek
with000
or cast the string as a number and multiply it by1000
.@cannawen What's your opinion on this? Should we also parse numbers like
20.2k
to20200
?I would like to work on this.