-
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
[kibana_react] Extract <FieldButton />
and <FieldIcon/>
to a package
#115377
Conversation
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
Unknown metric groupsAPI 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.
Asset management LGTM
@elasticmachine merge upstream |
@Dosant I see that it fails on |
@stratoula, thanks, looks like new usage of a component with merging main, I'll fix |
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.
VisEditors code changes LGTM. I tested Lens and everything seems to work as expected :)
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.
Operations LGTM
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.
Great work @Dosant , code changes LGTM. Happy to merge with passing CI 👍🏻
Co-authored-by: Jean-Louis Leysens <[email protected]>
…scss-in-packages # Conflicts: # src/plugins/presentation_util/public/components/field_picker/field_picker.tsx
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
Unknown metric groupsAPI count
History
To update your PR or re-run it, just comment with: |
This will serve as an example of react components in a package for #114990 and others, but unfortunately, no initial bundle size improvement for this one at all because since recently @elastic/kibana-presentation started importing these components to @elastic/kibana-presentation, fyi, you can read up on plugins vs packges here to see if you it would make sense to move some of |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Part of #114990
We would like to clean up
kibana_react
andkibana_utils
by moving some of shared stateless code that isn't tightly coupled to core's APIs into packages. This will not only allow us to declutter these plugins which became a place for putting code that is shared between plugins, but will also allow us to reduce initial bundle size because code from packages can be imported in async chunks only! (read on packages vs plugins).This is an initial "example" pr which moves
<FieldButton />
and<FieldIcon/>
to a package. It also resolves some missing pieces we had that would allow having a react component withscss
in a@kbn/
package (thanks to operations team Dosant#6)This will serve as a blueprint for moving other components.
p.s. initially, I started with
KibanaPageTemplate
component but decided to hold off and keep it in a plugin: #114990 (comment)