Skip to content

fix(applyPushRange): Apply the pushRange with maxRange #456

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

Merged
merged 1 commit into from
Nov 8, 2016

Conversation

GuilloOme
Copy link
Contributor

@GuilloOme GuilloOme commented Nov 8, 2016

Apply the pushRange when the difference is greater than the maxRange set

Close issue #453

Fixed demo: http://jsfiddle.net/nx7yqqa5

Apply the pushRange when the difference is greater than the maxRange set

Close issue angular-slider#453
@codecov-io
Copy link

Current coverage is 100% (diff: 100%)

Merging #456 into master will not change coverage

@@           master   #456   diff @@
====================================
  Files           1      1          
  Lines         912    921     +9   
  Methods         0      0          
  Messages        0      0          
  Branches        0      0          
====================================
+ Hits          912    921     +9   
  Misses          0      0          
  Partials        0      0          

Powered by Codecov. Last update 3e83a1a...bcd36f9

@ValentinH
Copy link
Member

Thanks for this PR, it is just perfect! It feels good to have such a nice contribution with tests and everything ;)

Actually your solution is better than the one I suggested in the issue because mine would have just blocked the slider when maxRange would be reached while your "pull" behavior is neat!

@ValentinH ValentinH merged commit 6327b88 into angular-slider:master Nov 8, 2016
@ValentinH
Copy link
Member

Released under 5.8.6

@GuilloOme
Copy link
Contributor Author

Thank you ! Glad to help…

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.

3 participants