-
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
[VisualizeList] Move CM client into separate plugin #165292
Conversation
💔 Build FailedFailed CI Steps
Test Failures
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
Unknown metric groupsAPI count
References to deprecated APIs
History
To update your PR or re-run it, just comment with: |
… CM (#165485) ## Summary Fix #163246 This PR fixes the CM problems within the Visualize List page leveraging the services already in place. The approach here is lighter than #165292 as it passes each client via the TypesService already used to register extensions in the Visualization scope. Also the `search` method now transparently uses the `mSearch` if more content types are detected without leaking any implementation detail outside the `VisualizationClient` interface. More fixes/features: * fixed Maps update operation definition which was missing the `overwrite` flag * Allow `mSearch` to accept an options object argument * Added new helper functions to interact with the metadata flyout in Listing page ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Stratoula Kalafateli <[email protected]>
Summary
Fixes #163246
This PR fixes a couple of issues with the current CM code:
visualization
types (i.e. Lens, Maps)overwrite
flagsearch
operation into themSearch
operation which is more correctChecklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers