[nit][pre-req] Split EPM Home into components#114431
[nit][pre-req] Split EPM Home into components#114431clintandrewhall merged 5 commits intoelastic:masterfrom
Conversation
|
Pinging @elastic/fleet (Team:Fleet) |
|
@elasticmachine merge upstream |
thomasneirynck
left a comment
There was a problem hiding this comment.
OK for shipper change, but I would remove the change to categories. IntegrationCategory was already strongly typed, and this change adds a duplication of data-structures (basically, we would now require two lists now, once as an array and once as a map).
thomasneirynck
left a comment
There was a problem hiding this comment.
fwiw - I'd unhook this change from that other strong-typing-for-shipper PR, it introduces a chain of dependencies, and they could be handled in parallel.
This will also create merge conflicts with #114429
💚 Build SucceededMetrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: |
💔 Backport failed
To backport manually run: |
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
|
New backport here #114828 |
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Clint Andrew Hall <clint.hall@elastic.co> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Summary
To make changes like #114432 easier to understand, I split the EPM Home Page into is disparate components. There are also some nominal performance tweaks, (like moving static
i18ncalls out of the render cycle to module-level consts, etc).This makes the next PR easier to grok, but also makes the individual portions of the page easier to test.
Tech debt: split the new components into "connected" and "pure" components to make testing easier.