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
Copy file name to clipboardExpand all lines: src/Vizor.ECharts/Options/Generated/ChartOptions.cs
+124-1Lines changed: 124 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -416,7 +416,130 @@ public List<YAxis>? YAxisList
416
416
/// ]]>
417
417
/// </summary>
418
418
[JsonPropertyName("visualMap")]
419
-
publicList<object>?VisualMap{get;set;}
419
+
[JsonInclude]
420
+
internalobject?VisualMapObject{get;set;}
421
+
422
+
/// <summary>
423
+
/// <![CDATA[
424
+
/// visualMap is a type of component for visual encoding, which maps the data to visual channels, including: symbol : Type of symbol.
425
+
/// symbolSize : Symbol size.
426
+
/// color : Symbol color.
427
+
/// colorAlpha : Symbol alpha channel.
428
+
/// opacity : Opacity of symbol and others (like labels).
429
+
/// colorLightness : Lightness in HSL .
430
+
/// colorSaturation : Saturation in HSL .
431
+
/// colorHue : Hue in HSL .
432
+
///
433
+
/// Multiple visualMap component could be defined in a chart instance, which enable that different dimensions of a series data are mapped to different visual channels.
434
+
///
435
+
/// visualMap could be defined as Piecewise (visualMapPiecewise) or Continuous (visualMapContinuous) , which is distinguished by the property type .
436
+
/// For instance: option = {
437
+
/// visualMap: [
438
+
/// { // the first visualMap component
439
+
/// type: 'continuous', // defined to be continuous visualMap
440
+
/// ...
441
+
/// },
442
+
/// { // the second visualMap component
443
+
/// type: 'piecewise', // defined to be piecewise visualMap
444
+
/// ...
445
+
/// }
446
+
/// ],
447
+
/// ...
448
+
/// };
449
+
///
450
+
/// ✦ Configure mapping ✦
451
+
/// The dimension of series.data can be specified by visualMap.dimension , from which the value can be retrieved and mapped onto visual channels, which can be defined in visualMap.inRange and visualMap.outOfRange .
452
+
///
453
+
///
454
+
/// In series that controlled by visualMap, if a data item needs to escape from controlled by visualMap, you can set like this: series: {
455
+
/// type: '...',
456
+
/// data: [
457
+
/// {name: 'Shanghai', value: 251},
458
+
/// {name: 'Haikou', value: 21},
459
+
/// // Mark as `visualMap: false`, then this item does not controlled by visualMap any more,
460
+
/// // and series visual config (like color, symbol, ...) can be used to this item.
461
+
/// {name: 'Beijing', value: 821, },
462
+
/// ...
463
+
/// ]
464
+
/// }
465
+
///
466
+
/// ✦ The relationship between visualMap of ECharts3 and dataRange of ECharts2 ✦
467
+
/// visualMap is renamed from the dataRange of ECharts2, and the scope of functionalities are extended a lot.
468
+
/// The configurations of dataRange are still compatible in ECharts3, which automatically convert them to visualMap .
469
+
/// It is recommended to use visualMap instead of dataRange in ECharts3.
470
+
///
471
+
///
472
+
/// ✦ The detailed configurations of visualMap are elaborated as follows.
473
+
/// ✦
474
+
/// ]]>
475
+
/// </summary>
476
+
[JsonIgnore]
477
+
publicIVisualMap?VisualMap
478
+
{
479
+
get=>VisualMapObjectasIVisualMap;
480
+
set=>VisualMapObject=value;
481
+
}
482
+
483
+
/// <summary>
484
+
/// <![CDATA[
485
+
/// visualMap is a type of component for visual encoding, which maps the data to visual channels, including: symbol : Type of symbol.
486
+
/// symbolSize : Symbol size.
487
+
/// color : Symbol color.
488
+
/// colorAlpha : Symbol alpha channel.
489
+
/// opacity : Opacity of symbol and others (like labels).
490
+
/// colorLightness : Lightness in HSL .
491
+
/// colorSaturation : Saturation in HSL .
492
+
/// colorHue : Hue in HSL .
493
+
///
494
+
/// Multiple visualMap component could be defined in a chart instance, which enable that different dimensions of a series data are mapped to different visual channels.
495
+
///
496
+
/// visualMap could be defined as Piecewise (visualMapPiecewise) or Continuous (visualMapContinuous) , which is distinguished by the property type .
497
+
/// For instance: option = {
498
+
/// visualMap: [
499
+
/// { // the first visualMap component
500
+
/// type: 'continuous', // defined to be continuous visualMap
501
+
/// ...
502
+
/// },
503
+
/// { // the second visualMap component
504
+
/// type: 'piecewise', // defined to be piecewise visualMap
505
+
/// ...
506
+
/// }
507
+
/// ],
508
+
/// ...
509
+
/// };
510
+
///
511
+
/// ✦ Configure mapping ✦
512
+
/// The dimension of series.data can be specified by visualMap.dimension , from which the value can be retrieved and mapped onto visual channels, which can be defined in visualMap.inRange and visualMap.outOfRange .
513
+
///
514
+
///
515
+
/// In series that controlled by visualMap, if a data item needs to escape from controlled by visualMap, you can set like this: series: {
516
+
/// type: '...',
517
+
/// data: [
518
+
/// {name: 'Shanghai', value: 251},
519
+
/// {name: 'Haikou', value: 21},
520
+
/// // Mark as `visualMap: false`, then this item does not controlled by visualMap any more,
521
+
/// // and series visual config (like color, symbol, ...) can be used to this item.
522
+
/// {name: 'Beijing', value: 821, },
523
+
/// ...
524
+
/// ]
525
+
/// }
526
+
///
527
+
/// ✦ The relationship between visualMap of ECharts3 and dataRange of ECharts2 ✦
528
+
/// visualMap is renamed from the dataRange of ECharts2, and the scope of functionalities are extended a lot.
529
+
/// The configurations of dataRange are still compatible in ECharts3, which automatically convert them to visualMap .
530
+
/// It is recommended to use visualMap instead of dataRange in ECharts3.
531
+
///
532
+
///
533
+
/// ✦ The detailed configurations of visualMap are elaborated as follows.
0 commit comments