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.

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

Proposed fix for #1378 - Added parseFloat before value and param are com... #1379

Closed
wants to merge 1 commit into from

Conversation

zenchua
Copy link

@zenchua zenchua commented Jan 16, 2015

Fix #1378 - value and param variables should be typecast before
comparison. This is required if rules are specified through
data-attributes

…compared.

Fix #1378 - value and param variables should be typecast before
comparison. This is required if rules are specified through
data-attributes
@zenchua zenchua closed this Jan 19, 2015
@jzaefferer
Copy link
Collaborator

Why did you close this?

@zenchua
Copy link
Author

zenchua commented Jan 20, 2015

Hi Jörn,

I closed the pull request because i realized it didnt pass all the tests. My apologies for that... I realized also that my solution will not work if date and string comparison is required.

ZR

@jzaefferer
Copy link
Collaborator

Okay, thanks for letting me know. If you can find a solution that solves the problem you reported, let me know, another PR is definitely welcome.

@zenchua
Copy link
Author

zenchua commented Feb 3, 2015

Hi Jörn,

Thanks for the encouragement.. I'm new to GitHub and i'm sorry for creating lots of unwanted commits...

Here's my latest PR. This time round, it fixes the issue reported and passes the travis test.
#1391

ZR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

param & value for min & max rules should be type cast when rules are specified through data attributes
2 participants