[WIP] Isolate DataView code to the Kibana service implementation

[clintandrewhall]

Summary

This is a WIP/draft to isolate the use of DataView and startPlugins.dataViewEditor.openEditor to the kibana implementation of the service.

Why?

I'm going to be moving components and services to packages, and in order to do that, I have to isolate the Kibana implementations of our service abstractions so the components can exist in isolation themselves.

Open Questions

The only way I can get the EditorsServiceFactory to accept the method from startPlugins.dataViewEditor is to create a generic and default it to unknown. I'm curious if there's a better, cleaner way to do this...?

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: 8cc8e92
• Interpreting CI Failures
• Storybooks Preview
• Webpack Bundle Analyzer

Failed CI Steps

• Jest Tests #1
• Jest Integration Tests #3

Test Failures

• [job] [logs] Jest Tests #1 / on dataView created
• [job] [logs] Jest Integration Tests #3 / Fleet preconfiguration reset Preconfigred cloud policy Create correct .fleet-policies

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
sharedUX	100.7KB	100.6KB	-23.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream