[Portable Dashboards][Meta] Part 1 - Portable Dashboard Container

[ThomThomson]

Portable Dashboard Container Part 1 Overview

The first piece of the Portable Dashboard initiative involves separating the Dashboard App from the Dashboard Container. This means that all of the code that makes the dashboard work should be removed from the dashboard App and properly encapsulated within the Dashboard Container Embeddable. This includes:

• Dashboard Saved object Loading and saving.
• Dashboard state management including syncing with the URL and session state.
• Extension points for setting filters, query, and time range.

Once all of this code is encapsulated cleanly within the Dashboard Container, we can build out a simple-to-use dashboard API, and allow the solutions teams to start using it to build dashboard-like experiences within their apps.

This first portion of the Portable Dashboards project can be further split into chronological issues.

Progress

Prep work

• Prepare the Redux Embeddable Wrapper for use with Dashboard. @ThomThomson
• Remove Legacy Clientside Migrations @ThomThomson
• Migrate from the Dashboard Saved Object to using the saved objects client directly. @ThomThomson
• Use the Services Abstractions system for the Dashboard. @Heenawter

Implementation

• Transform the Dashboard Embeddable into a By Reference / By Value embeddable.
• Migrate the Dashboard Embeddable to use the Redux Embeddable Tools

Solution Developer Experience Enhancements

• [Portable Dashboards] Build API Examples #145427

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)