-
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
Cleanup of the kibanaLegacy unused functions and remove unecessary dependencies from Analytics plugins #113358
Cleanup of the kibanaLegacy unused functions and remove unecessary dependencies from Analytics plugins #113358
Conversation
I haven't removed the dependency from the discover plugin as this function src/plugins/kibana_legacy/public/utils/inject_header_style.ts is needed for the truncate:maxHeight UI setting to work correctly. As the kibanaLegacy plugin is not disableable maybe it is safe to remove the dependency from the discover plugin but I am not 100% sure. @elastic/kibana-data-discovery wdyt? Update: We discussed it offline. We are going to remove the dependency when the above functionality will be moved in the discover plugin. |
💚 Build SucceededMetrics [docs]Module Count
Public APIs missing comments
Any counts in public APIs
Async chunks
Page load bundle
Unknown metric groupsAPI count
async chunk count
History
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lovely PR 👏🏼 I think CI and functional tests give enough confidence to not even test it in this case but I ran it locally and opened all the involved parties (dashboard etc). Works with no problems!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is amazing! Looked over the dashboard changes, and it's incredible that I didn't notice we weren't using Kibana_legacy
anymore. Thank you for removing it, and nothing is better than seeing +2 -1660
on a PR.
L G T M
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, reviewed data discovery owned code. didn't test, but the usage of 'kibanaLegacy' in 'discover_enhanced' was always redundant, thx for the cleanup
💔 Backport failed
To backport manually run: |
…pendencies from Analytics plugins (elastic#113358) * [Discover][Table] Remove unused dependencies of the kibanaLegacy plugin * More removals of kibanaLegacy plugin dependencies * Revert discover changes * Remove the unused functions from the kibana_legacy plugin * Removes unused translations # Conflicts: # src/plugins/kibana_legacy/public/plugin.ts
…ary dependencies from Analytics plugins (#113358) (#113503) * Cleanup of the kibanaLegacy unused functions and remove unecessary dependencies from Analytics plugins (#113358) * [Discover][Table] Remove unused dependencies of the kibanaLegacy plugin * More removals of kibanaLegacy plugin dependencies * Revert discover changes * Remove the unused functions from the kibana_legacy plugin * Removes unused translations # Conflicts: # src/plugins/kibana_legacy/public/plugin.ts * Revert usage that cant be removed in 7.x
Summary
Part of #76905
By removing angular from our plugins, we also no need to depend on the kibanaLegacy plugin. This PR, removes the dependency from the Analytics teams plugins as it was not used anymore.
Also it removes the unused functions from the
kibana_legacy
plugin. A second PR will follow after angular is removed from the monitoring plugin which will delete all the remaining angular from the plugin.Our ultimate goal is to remove the
kibana_legacy
plugin.