-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[uiActions] VALUE_CLICK_TRIGGER and APPLY_FILTER_TRIGGER should be registered by uiActions
plugin.
#60148
Labels
bug
Fixes for quality problems that affect the customer experience
Comments
spalger
added
bug
Fixes for quality problems that affect the customer experience
Team:AppArch
labels
Mar 13, 2020
Pinging @elastic/kibana-app-arch (Team:AppArch) |
spalger
changed the title
[uiActions] SELECT_RANGE_TRIGGER should be registered by
[uiActions] VALUE_CLICK_TRIGGER and APPLY_FILTER_TRIGGER should be registered by Mar 14, 2020
uiActions
plugin.uiActions
plugin.
This was referenced Mar 14, 2020
This was referenced Mar 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
SELECT_RANGE_TRIGGER
trigger is currently registered with theuiActions
plugin by theembeddables
plugin, which creates a minor race condition because it's required by thedata
plugin but we don't want to create an explicit dependency there for this purpose. Instead we should moveSELECT_RANGE_TRIGGER
into theuiActions
plugin.The text was updated successfully, but these errors were encountered: