Add content management mSearch to viz, lens, and event annotation group #162450
Conversation
| allowedSavedObjectAttributes: string[]; | ||
| } | ||
|
|
||
| function savedObjectToItem<Attributes extends object>( |
There was a problem hiding this comment.
Just want to understand better, is this function always applicable for any saved object, or is there a scenario where it will have to be changed for a specific saved object type later (maybe with some data changes)?
There was a problem hiding this comment.
Previously, I had run into a case where a malformed saved object could throw validation errors since all SO attributes were being added to the resulting object. Therefore I decided it was best to treat the SO doc itself like an api that needs to specify its inputs.
|
@elasticmachine merge upstream |
mattkime
added
Feature:Lens
Team:DataDiscovery
|
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
mattkime
added
the
release_note:skip
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
History
To update your PR or re-run it, just comment with: cc @mattkime |
kibanamachine
added
v8.10.0
backport:skip
…up (elastic#162450) ## Summary Adds content management api mSearch functionality to `lens`, `visualization`, and `event_annotation_group` types via abstracted function and types. Part of elastic#161545 --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Stratoula Kalafateli <[email protected]>
Summary
Adds content management api mSearch functionality to
lens,visualization, andevent_annotation_grouptypes via abstracted function and types.Part of #161545