-
Notifications
You must be signed in to change notification settings - Fork 52
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
Observer is causing performance issues #67
Comments
I didn't notice any performance issues but I do agree that the observer is not necessary and should be removed. |
Yeah, very noticeable. Can you prepare a PR? |
Closed
scottkidder
pushed a commit
to scottkidder/ember-cli-nouislider
that referenced
this issue
Sep 21, 2018
It's not necessary as the value is updated in didUpdateAttrs hook. Should fix kennethkalmer#67
scottkidder
pushed a commit
to scottkidder/ember-cli-nouislider
that referenced
this issue
Mar 27, 2019
It's not necessary as the value is updated in didUpdateAttrs hook. Should fix kennethkalmer#67
scottkidder
pushed a commit
to scottkidder/ember-cli-nouislider
that referenced
this issue
Mar 27, 2019
It's not necessary as the value is updated in didUpdateAttrs hook. Should fix kennethkalmer#67
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I've noticed that using observer in the range-slider causes performance issues.
The problematic part is observer on
start
attribute. I think it's not necessary, because ondidUpdateAttrs
method callsupdate
which updatesstart
property as well.I've tried to remove completely that observer and it solved the performance issue for me.
here is an working example https://ember-twiddle.com/d1cb52c73d07c0c016261c36000f5971?openFiles=templates.application.hbs%2C
Would you accept PR?
The text was updated successfully, but these errors were encountered: