You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the logic for rendering plugin resources & overlays on a visualization, we need to have a clean way for determining a particular vis config is eligible for the feature.
Eligibility checks will be needed when:
collecting VisLayers or not in the VisualizeEmbeddable render flow
displaying the extra options in the context menu (the plugin-specific options, the 'View Events' option) - this will be done via isCompatible() fns of the actions that are triggered via CONTEXT_MENU_TRIGGER.
This roughly will include:
must be of type 'line'
must have a "valid" config (one set of x axes, x axis field is of type date, reasonable metrics, etc.). this will be the bulk of the work needed
must not show in the 'edit' context. basically, when viewing the details, we don't want to show, or even attempt to show, any VisLayers here. the feature is just for showing in the context of the dashboard. later improvements to the feature may support something to show / configure in the edit view
The text was updated successfully, but these errors were encountered:
As part of the logic for rendering plugin resources & overlays on a visualization, we need to have a clean way for determining a particular vis config is eligible for the feature.
Eligibility checks will be needed when:
VisLayer
s or not in theVisualizeEmbeddable
render flowisCompatible()
fns of the actions that are triggered viaCONTEXT_MENU_TRIGGER
.This roughly will include:
date
, reasonable metrics, etc.). this will be the bulk of the work neededThe text was updated successfully, but these errors were encountered: