Runtime: Dashboard components with generic renderers and optional inline definition #4735
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
components:
property toitems:
in the dashboard YAMLitem = component + grid info
Chart
resource toComponent
items[*].component
is astring
, it is treated as a reference to an externally defined componentitems[*].component
is amap
, it is treated as an inline component definitionrenderer
andrenderer_properties
fields toComponent
"renderer": "vega_lite", "rendererProperties": {"spec": "..."}
"renderer": "markdown", "rendererProperties": {"contents": "..."}
"renderer": "image", "rendererProperties": {"url": "..."}
Component
resources called[dashboard name]--component[idx]
/charts/{name}/data
API to/components/{name}/data
GenerateChartSpec
API toGenerateRenderer
. It now returns two values:renderer
andrenderer_properties
.See this design doc for the new component syntax.
This PR currently breaks the frontend since these are breaking changes.