Remove kibana_legacy plugin #76905
Labels
[Deprecated-Use Team:Presentation]Team:Geo
Former Team Label for Geo Team. Now use Team:Presentation
Feature:FieldFormatters
Feature:NP Migration
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:small
Small Level of Effort
:ml
refactoring
Team:Monitoring
Stack Monitoring team
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
technical debt
Improvement of the software architecture and operational architecture
The
kibana_legacy
plugin contains deprecated functionality. All consumers should migrate away from it mid-term so the plugin can be retired completely. This issue tracks all of the places, feel free to open sub-issues.This list doesn't track things which are scheduled to be removed with 8.0 (dashboard mode, default app id, timelion)
start.loadFontAwesome
references the font awesome loader exposed via contract - it should be migrated to use EUI icons instead.dashboard
@elastic/kibana-appconfigureAppAngularModule
addFatalError
AngularHttpError
subscribeWithScope
discover
@elastic/kibana-appinitAngularBootstrap
configureAppAngularModule
KbnAccessibleClickProvider
PrivateProvider
PromiseServiceCreator
registerListenEventListener
watchMultiDecorator
createTopNavDirective
createTopNavHelper
formatMsg
formatStack
subscribeWithScope
addFatalError
start.loadFontAwesome
.truncate-by-height
(global CSS class set by legacy plugin)data
@elastic/kibana-app-arch.truncate-by-height
(global CSS class set by legacy plugin)vis_type_table
@elastic/kibana-appinitAngularBootstrap
region_map
@elastic/kibana-gisstart.loadFontAwesome
tile_map
@elastic/kibana-gisstart.loadFontAwesome
vis_type_vislib
@elastic/kibana-appstart.loadFontAwesome
ml
@elastic/machine-learningstart.loadFontAwesome
(7.11 [ML] Remove all usage of font awesome icons in ML plugin #84066)monitoring
@elastic/stack-monitoring-ui [Monitoring] Remove kibana_legacy plugin #99716start.loadFontAwesome
graph
@elastic/kibana-appstart.loadFontAwesome
The text was updated successfully, but these errors were encountered: