Skip to content
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.

Sign up for GitHub

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

Jump to bottom

parseFloat for cases where numbers are mistakenly sent as strings #288

Merged
merged 2 commits into from
Feb 26, 2018
Merged

parseFloat for cases where numbers are mistakenly sent as strings #288

merged 2 commits into from
Feb 26, 2018

Conversation

kflemin
Copy link
Contributor

@kflemin kflemin commented Feb 23, 2018

Teeny change...this is really a data error (numbers are being sent over as strings), but just in case they are, this will improve the chart display.

@coveralls
Copy link

coveralls commented Feb 23, 2018 •
edited
Loading

Coverage Status

Coverage decreased (-0.2%) to 60.328% when pulling 3e5d7c0 on parse-float into 9222045 on develop.

@rHorsey
Copy link
Contributor

rHorsey commented Feb 26, 2018

Thanks @kflemin !!!

@rHorsey rHorsey merged commit 665b17b into develop Feb 26, 2018
@rHorsey rHorsey deleted the parse-float branch February 26, 2018 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@kflemin @coveralls @rHorsey