mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 01:13:23 -04:00
9c4f99d8c1
## Summary Original outline: https://github.com/elastic/kibana/issues/138181 Issues outlining the objective of this pr: https://github.com/elastic/kibana/issues/142903 and https://github.com/elastic/kibana/issues/142907 #### Overview Since the data views plugin was introduced, maintaining our own apis for fetching sourcerer saved objects (data views) and additional types has become cumbersome and inefficient. The data views plugin provides both an efficient caching of data view saved objects and a unified interface for creating ad-hoc data views (see the changes to the `useFetchIndex` hook in this PR) so that our code can now rely on a single type of saved object to interface with when fetching data. This PR is another step towards replacing sourcerer with the data view picker provided by kibana platform (which benefits users by maintaining consistency around data source selection UX) and additionally provides benefits to developers in the security solution by allowing us to reduce state-management complexity in components that rely on old `indexPattern` types or data view types. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| search_strategy | ||
| utils | ||
| index.ts | ||
| plugin.ts | ||
| types.ts | ||