-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[XY] Adapt for xyVis
.
#127712
Comments
Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors) |
This list looks good to me - let me know whether I misunderstand something, but it looks like it's only about adding additional features / renaming parameters, there are no real "conflicts", correct? |
Pinging @elastic/kibana-presentation (Team:Presentation) |
@flash1293, during my digging into the code of |
Comparing
vis_xy
fromvis_types
andlens_xy
, there are such differences in the API and in the functionality:Adaptation notes
Globally
visdimension
at fields:splitAccessor
,accessors
,xAccessor
.splitRowDimension
,seriesDimension
, zDimension.splitRowDimension
- allow split by row (in xy_vis -Split chart
)seriesDimension
- allow split serieszDimension
- allow to provide field name of mark size metric onDatum
. Only used with line/area seriesseriesParams
args:lineWidth
,circlesRadius
)seriesParams
arg:showCircles
)seriesParams
arg:drawLinesBetweenPoints
)addTimeMarker
arg)orderBucketsBySum
(allow to order ordinal x values by descending)addTooltip
arg)detailedTooltip
arg)categoryAxes
are x - axes,valueAxes
are y-axes):categoryAxes.scale.mode/valueAxes.axisParams.scale.mode
arg)categoryAxes.position/valueAxes.axisParams.position
arg)categoryAxes.scale.boundsMargin/valueAxes.axisParams.scale.boundsMargin
arg)categoryAxes.labels.color/valueAxes.axisParams.labels.color
arg)categoryAxes.labels.filter/valueAxes.axisParams.labels.filter
arg)categoryAxes.labels.truncate/valueAxes.axisParams.labels.truncate
arg)zDimension
. (radiusRatio
arg)palette
type fromstring
topalette
.The text was updated successfully, but these errors were encountered: