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

fixed onChange which fired on every mousmove, added test #145

Merged
merged 2 commits into from
Sep 12, 2016

Conversation

Fuzzyma
Copy link
Contributor

@Fuzzyma Fuzzyma commented Aug 24, 2016

This PR fixes /issues/144

I tried to lint but linting fails because of modules not installed and wrong config values.
Also tried using ReactTestUtils.Simulate for tests without success.
At least I tried...

@benjycui
Copy link
Member

Thanks!

But, could you resolve CI failed?

@Fuzzyma
Copy link
Contributor Author

Fuzzyma commented Sep 10, 2016

At the time writing this PR your test suite failed because of an internal error and not because of the actual test failing. Is that fixed?

@benjycui
Copy link
Member

Sorry, my bad..

@benjycui
Copy link
Member

Done, please rebase, thanks!

@coveralls
Copy link

Coverage Status

Coverage increased (+12.7%) to 75.783% when pulling 51a951e on Fuzzyma:master into 67b7695 on react-component:master.

@Fuzzyma
Copy link
Contributor Author

Fuzzyma commented Sep 11, 2016

jej - i feel good when I read this :D

@benjycui benjycui merged commit 1568019 into react-component:master Sep 12, 2016
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.

onChange called even when value did not change
3 participants