-
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
Remove usages of @kbn/ui-framework
#46410
Comments
Pinging @elastic/kibana-app |
I opened up a PR to remove the We will want to replace these usages with the equivalent EUI styles. I started down this road in #78230, but quickly realized I am not familiar enough with EUI nor Discover and Timelion to take on with the time I have. |
Anyone have some spare cycles so we can push |
cc @elastic/kibana-design, not sure if this is something you all want to be in the loop on. |
Kibana designers would too love to wish KUI farewell! 😁 We can try to help if there are specific instances that are questionable about replacements. I'm pretty sure there's already a Discover feature branch that has converted this all to EUI (cc @kertal). Timelion is the harder one because I think it might still have Angular bits and bootstrap. |
While it is in Angular - from what I can tell it's all in HTML templates, so should be doable. |
@cchaos there's not much kui left in discover legacy table & discover context. if it should be done fast, we could inline the needed kui directives, this could also be done with timelion. context.html is next to be deangularized, so kui should be gone there, too |
@kertal I am 👍 on inlining for what it's worth. |
I can see references to kui in:
I'm not planning to work on this right now, so I'm going to remove my assignment. |
Removing it in Discover is on our todo list: |
Removing visualizations team as we don't ise this plugin anymore! |
Maybe we could request EUI to provide the same icon set used in Graph so that we can remove FontAwesome once and for all? |
Def something we need to discuss with them! @elastic/kibana-design wdyt about it? |
The Graph app doesn't appear to offer an excessive number of icons. Even less that don't have an EUI equivalent (I count 8). I imagine we could add icons for the unmatched ones fairly easily. If that's how ya'll would like to proceed, what sort of priority should this be given?
While we're on the topic of FontAwesome, is that what the Maps app uses for their icons as well? If so, would those icons need to be accounted for as well? If so, that may be more problematic, as the Maps app offers a much larger list of icon options. CCing @elastic/eui-team. |
Maps gets its icons from https://github.com/elastic/maki |
Thanx @MichaelMarcialis for the list! About the priority let's discuss it today on our WG sync |
AppEx Platform Security is tracking our work here: #160122 |
@dej611 we suggest using maki icons that the maps team already uses. Wdyt? |
We could move maki utilities into a package so its accessible anywhere in kibana |
@nreese this is a good idea! |
Need to check how the maki icons work. Will update the issue here once verified 👍 |
Thanx otherwise, we will need to create them on EUI |
I created a new issue for the graph #160232 so we are going to track our work there. |
This has merged |
We removed it from graph! |
Thanks everyone for the work so far. We're close! These are the remaining usages of KUI:
|
@elastic/appex-sharedux part should be done here #167014 |
The @elastic/kibana-presentation part will be done here. There were no usages of any |
## Summary Partially addresses #46410 Stops using `kuiTextInput` CSS class name in `number_parameter.js` and `string_paramter.js` components in the `home` plugin. How to test? I don't know if these parameters are still used, so to test this apply this patch: ```diff diff --git a/src/plugins/home/public/application/components/tutorial/instruction_set.js b/src/plugins/home/public/application/components/tutorial/instruction_set.js index 651212f062c..7f2077a322d 100644 --- a/src/plugins/home/public/application/components/tutorial/instruction_set.js +++ b/src/plugins/home/public/application/components/tutorial/instruction_set.js @@ -261,14 +261,20 @@ class InstructionSetUi extends React.Component { render() { let paramsForm; - if (this.props.params && this.state.isParamFormVisible) { + if (true) { paramsForm = ( <> + PARAMETER FORM <EuiSpacer /> <ParameterForm - params={this.props.params} - paramValues={this.props.paramValues} - setParameter={this.props.setParameter} + params={[ + { id: 'test', label: 'test', type: 'string' }, + { id: 'test2', label: 'test2', type: 'number'} + ]} + paramValues={{ test: 'test', test2: 123 }} + setParameter={(id, value) => { + console.log('setParameter', id, value); + }} /> </> ); ``` And go to `/app/home#/tutorial/apm` page, you will see the new parameter input look there: <img width="478" alt="image" src="https://github.com/elastic/kibana/assets/82822460/ba3a3dce-c2d5-41db-a7e8-24bf6caeb16b"> Co-authored-by: Kibana Machine <[email protected]>
## Summary Closes #46410 Removes the deprecated `@kbn/ui-framework` --------- Co-authored-by: kibanamachine <[email protected]>
The
@kbn/ui-framework
is still used in a few places, and references an incredibly old version of EUI. The version of EUI has a reference to a version of lodash which is flagged by security vulnerability scanners. Even though the existing usages are a false positive, it causes a lot of headaches.The text was updated successfully, but these errors were encountered: