[drilldowns] require embeddables to opt into ON_OPEN_PANEL_MENU trigger#259637
Merged
nreese merged 7 commits intoelastic:mainfrom Mar 26, 2026
Merged
[drilldowns] require embeddables to opt into ON_OPEN_PANEL_MENU trigger#259637nreese merged 7 commits intoelastic:mainfrom
nreese merged 7 commits intoelastic:mainfrom
Conversation
Contributor
Author
|
/ci |
Contributor
Author
|
/ci |
Contributor
Author
|
/ci |
Contributor
Author
|
/ci |
Contributor
|
Pinging @elastic/kibana-presentation (Team:Presentation) |
Contributor
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
History
|
jughosta
approved these changes
Mar 26, 2026
kowalczyk-krzysztof
approved these changes
Mar 26, 2026
ThomThomson
approved these changes
Mar 26, 2026
Contributor
ThomThomson
left a comment
There was a problem hiding this comment.
Nice simple changes, good magic removal. LGTM!
| serializeState: () => serialize(savedObjectId$.getValue()), | ||
| getInspectorAdapters: () => searchEmbeddable.stateManager.inspectorAdapters.getValue(), | ||
| supportedTriggers: () => { | ||
| // No triggers are supported, but this is still required to pass the drilldown |
Contributor
There was a problem hiding this comment.
This comment should definitely have tipped us off that this was a bad code smell. Happy to see it removed!
mbondyra
added a commit
to mbondyra/kibana
that referenced
this pull request
Mar 26, 2026
…hanges * commit '22bf09c82658b9511cbb2ad13f6dd29ad3526472': (21 commits) [Overlays System Flyout]: Support Child History (elastic#256339) KUA-Update event naming format and examples (elastic#259846) Fix pagerduty connector codeownership (elastic#259807) [Upgrade Assistant] Migrate Kibana deprecations flaky integration tests to unit tests (elastic#258981) [Upgrade Assistant] Migrate ES deprecations flaky integration tests to unit tests (elastic#258142) [Index Management] Migrate flaky integration tests to unit tests (elastic#258942) [Cases] Rename attachment id to saved object id (elastic#259158) [Entity Store] Change hash algo to sha256 (elastic#259453) [Security Solution] fixed enhanced security profile header showing for non-alert documents (elastic#259801) Update LaunchDarkly (main) (elastic#259008) [Discover] Add observability default ES|QL query (elastic#257268) Update dependency @redocly/cli to v2.21.1 (main) (elastic#259016) Gap reason detected (elastic#258231) [One Workflow] Historical executionContext and telemetry (elastic#258623) coderabbit: drop SigEvents (elastic#259863) [ci] Bump cypress disk (elastic#259861) Server timings (elastic#258915) Replace deprecated EUI icons in files owned by @elastic/kibana-cases (elastic#255633) [ci] Bump storybooks disk (elastic#259858) [drilldowns] require embeddables to opt into ON_OPEN_PANEL_MENU trigger (elastic#259637) ...
jeramysoucy
pushed a commit
to jeramysoucy/kibana
that referenced
this pull request
Apr 1, 2026
…er (elastic#259637) Closes elastic#259590 Before this PR, drilldown UI code added `ON_OPEN_PANEL_MENU` to an embeddable's supported triggers. This auto-magically allowed embeddables that implemented `HasSupportedTriggers` interface to support drilldowns that used `ON_OPEN_PANEL_MENU` trigger. This auto-magic is causing problems with "as code" schemas. Embeddables register supported triggers on server during schema generation. Embeddables would not list `ON_OPEN_PANEL_MENU` in their supported triggers, allowing the UI to create drilldowns with triggers that are not contained in the schema. This PR resolves the issue by removing the magic. Drilldown UI code no longer adds `ON_OPEN_PANEL_MENU` to an embeddable's supported triggers. Instead, embeddables must explicitly include `ON_OPEN_PANEL_MENU` in supported triggers list. PR also updates `drilldownRegistry.getSchema` to throw when no drilldowns match supporting triggers to give developers immediate feedback that drilldowns should not be included in schema if there is no overlap in supported triggers and drilldowns. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
paulinashakirova
pushed a commit
to paulinashakirova/kibana
that referenced
this pull request
Apr 2, 2026
…er (elastic#259637) Closes elastic#259590 Before this PR, drilldown UI code added `ON_OPEN_PANEL_MENU` to an embeddable's supported triggers. This auto-magically allowed embeddables that implemented `HasSupportedTriggers` interface to support drilldowns that used `ON_OPEN_PANEL_MENU` trigger. This auto-magic is causing problems with "as code" schemas. Embeddables register supported triggers on server during schema generation. Embeddables would not list `ON_OPEN_PANEL_MENU` in their supported triggers, allowing the UI to create drilldowns with triggers that are not contained in the schema. This PR resolves the issue by removing the magic. Drilldown UI code no longer adds `ON_OPEN_PANEL_MENU` to an embeddable's supported triggers. Instead, embeddables must explicitly include `ON_OPEN_PANEL_MENU` in supported triggers list. PR also updates `drilldownRegistry.getSchema` to throw when no drilldowns match supporting triggers to give developers immediate feedback that drilldowns should not be included in schema if there is no overlap in supported triggers and drilldowns. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
nreese
added a commit
that referenced
this pull request
Apr 9, 2026
…ers (#261018) Follow up to #259637 Before this PR, drilldown UI code added ON_APPLY_FILTER to an embeddable's supported triggers. This auto-magically allowed embeddables that implemented HasSupportedTriggers interface to support drilldowns that used ON_APPLY_FILTER trigger. This auto-magic could cause problems with "as code" schemas. Embeddables register supported triggers on server during schema generation. Embeddables could not list ON_APPLY_FILTER in their supported triggers, allowing the UI to create drilldowns with triggers that are not contained in the schema. In practice this did not happen, but we want to avoid the possibility for such a mistake. This PR resolves the issue by removing the magic. Drilldown UI code no longer adds ON_APPLY_FILTER to an embeddable's supported triggers. Instead, embeddables must explicitly includeON_APPLY_FILTER in supported triggers list. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #259590
Before this PR, drilldown UI code added
ON_OPEN_PANEL_MENUto an embeddable's supported triggers. This auto-magically allowed embeddables that implementedHasSupportedTriggersinterface to support drilldowns that usedON_OPEN_PANEL_MENUtrigger.This auto-magic is causing problems with "as code" schemas. Embeddables register supported triggers on server during schema generation. Embeddables would not list
ON_OPEN_PANEL_MENUin their supported triggers, allowing the UI to create drilldowns with triggers that are not contained in the schema.This PR resolves the issue by removing the magic. Drilldown UI code no longer adds
ON_OPEN_PANEL_MENUto an embeddable's supported triggers. Instead, embeddables must explicitly include
ON_OPEN_PANEL_MENUin supported triggers list.PR also updates
drilldownRegistry.getSchemato throw when no drilldowns match supporting triggers to give developers immediate feedback that drilldowns should not be included in schema if there is no overlap in supported triggers and drilldowns.