-
Notifications
You must be signed in to change notification settings - Fork 839
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
fix(selectable): use latest state in onChange #4292
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
8420dc3
to
e453c9e
Compare
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.
e453c9e
to
827865f
Compare
Thanks @thompsongl. I have added the changelog entry now, and rebased into my previous commit. 👍 |
jenkins test this |
Preview documentation changes for this PR: https://eui.elastic.co/pr_4292/ |
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.
LGTM!
Thanks for the help!
Summary
Fixes the issue described in #4262. In short, passes the latest component state to the
searchProps.onChange
callback.Checklist