[Discover] Split saved searches out of discover plugin#138388
Conversation
… into split-out-visualize-app
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
Unknown metric groupsAPI count
ESLint disabled in files
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
|
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
kertal
left a comment
There was a problem hiding this comment.
LGTM, code review, testing by merging with the lens in Discover POC, cyclic dependency resolved. thx for taking care of the heavy lifting 👍
dej611
left a comment
There was a problem hiding this comment.
Tested locally 👍
Left only a tiny nitpick comment.
| import { SavedSearch } from '@kbn/saved-search-plugin/public'; | ||
| import type { SortOrder } from '@kbn/saved-search-plugin/public'; |
There was a problem hiding this comment.
that's what this PR will do ... once the merge conflicts are resolved: #137488
Joe's PR went first, because I doubt he already has grey hair ... while one gray hair more for me, doesn't matter 👴
This PR splits shared saved search logic (used by discover and visualize) out of the discover plugin into a separate plugin. This will allow to implement the histogram in Discover using a Lens embeddable in a later step (otherwise it would have introduced a cyclic dependency).
This PR is mostly moving over the saved search service - react hook and conflict component are left within Discover because they are not used anywhere else.