-
Notifications
You must be signed in to change notification settings - Fork 11.9k
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
Configurable hide/show animations #7055
Conversation
src/core/core.controller.js
Outdated
me.setDataVisibility(datasetIndex, index, visible); | ||
} | ||
meta._skipUpdate = true; | ||
me.update(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't we just not call update
instead of adding _skipUpdate
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some comments to explain
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It feels a little off to me that we're reaching inside the meta object to set a private property _skipUpdate
. E.g. it's not an API our users would be able to use really. What do you think about if we made mode
also able to take a function
to be resolved and then we could return a different mode
for datasetIndex
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
rebased |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks good to me
@kurkle looks like this one needs to be rebased |
closes: #1833
master:
pr: