Apache ECharts Documentation

jQuery-autoComplete is an extremely lightweight completion suggester plugin for jQuery. It is designed to provide suggestions as a user types in an input field.

Key Features:

• Lightweight: Approximately 3.4 kB of JavaScript (< 1.4 kB gzipped).
• Flexible Data Sources: Supports various ways to provide completion data.
• Performance Controls: Includes smart caching, input delay, and minimum character settings to optimize user experience.
• Extensibility: Supports callbacks and custom rendering via the renderItem option.

Compatibility:

• Requires jQuery 1.7.0+.
• Supported browsers: Firefox, Safari, Chrome, Opera, and Internet Explorer 7+.

This specific vendor version of Handsontable (0.10.5.1) has been modified for use within this repository with the following characteristics:

• Manual Feature Implementation: The trimWhitespace feature is not natively available in this version (it was introduced in Handsontable 1.12.6). It has been manually added and can be configured via the trimWhitespace option.
• Exclusions: This build does not contain numeral.js code or jquery.mousewheel code; these are expected to be referenced externally.
• Compatibility Note: This version is used to maintain support for older environments (like Windows XP/IE8/IE9) that were dropped in Handsontable v1.12.0.

// Example of using the manually added feature
const hot = new Handsontable(container, {
  // ... other options
  trimWhitespace: true
});

The echarts-simple-transform library provides non-official data transformers for Apache ECharts 5. These allow you to manipulate datasets directly within the ECharts dataset component using the transform property. To use these transforms, you must first register them using echarts.registerTransform().

echarts.registerTransform(ecSimpleTransform.aggregate);
// or
echarts.registerTransform(ecSimpleTransform.id);

tslib is a runtime library for TypeScript that contains helper functions (such as __extends and __assign) used by the TypeScript compiler.

By default, TypeScript may emit these helper functions into every file that needs them, leading to code duplication. When you use the --importHelpers flag, TypeScript instead emits a require or import statement to pull these helpers from the tslib module. This results in smaller bundle sizes and reduced runtime overhead.

// Without tslib (duplicated in every file):
var __assign = (this && this.__assign) || Object.assign || function(t) { ... };

// With tslib (imported from module):
var tslib_1 = require("tslib");
exports.y = tslib_1.__assign({}, exports.x);

The itemStyle object is used to specify the visual style of the sectors in a sunburst chart. You can apply styles at three different levels of granularity, with the following priority (highest overrides lowest):

1. series.data.itemStyle: Specific style for an individual sector.
2. series.levels.itemStyle: Style for all sectors at a specific level.
3. series.itemStyle: Global style for all sectors in the series.

Common properties include color, borderColor, borderWidth, opacity, and borderRadius.

{
  "series": {
    "type": "sunburst",
    "itemStyle": {
      "color": '#ccc',
      "borderColor": '#fff',
      "borderWidth": 1
    },
    "data": [
      {
        "name": "Specific Sector",
        "itemStyle": {
          "color": 'red'
        }
      }
    ]
  }
}

You can specify the visual style of sunburst sectors using itemStyle. Styles can be applied at three levels of granularity with the following priority (highest to lowest):

1. series.data.itemStyle: Specific style for an individual data sector.
2. series.levels.itemStyle: Style applied to all sectors at a specific level of the sunburst.
3. series.itemStyle: Default style for all sectors in the series.

Use levels.blur.itemStyle.color to define the color for sectors at a specific level. If not specified, colors are taken from the option.color palette by default.

The select.label.rich property allows you to define

label: {
    // Styles defined in 'rich' can be applied to some fragments
    // of text by adding some markers to those fragment, like
    // `{styleName|text content text content}`.
    formatter: [ 
        '{a|Style "a" is applied to this snippet}'
        '{b|Style "b" is applied to this snippet}This snippet use default style{x|use style "x"}'
    ].join('\n'),
    rich: {
        a: {
            color: 'red'
        },
        x: {
            fontWeight: 'bold'
        }
    }
}

Immutable collections should be treated as values rather than objects. To check if two collections contain the same data, use Immutable.is(val1, val2) or the .equals() method. Do not use the === operator for value equality, as === checks for object reference identity.

var map1 = Immutable.Map({a:1, b:2, c:3});
var map2 = map1.set('b', 2);
assert(map1.equals(map2) === true);

var map3 = map1.set('b', 50);
assert(map1.equals(map3) === false);