doc: coarse pointer

build.js

@@ -13,7 +13,7 @@
  */
 
 const md2json = require('./tool/md2json');
-const {extractDesc, extractOptionKeys} = require('./tool/schemaHelper');
+const {extractDesc} = require('./tool/schemaHelper');
 const fs = require('fs');
 const fse = require('fs-extra');
 const marked = require('marked');
@@ -24,7 +24,7 @@ const argv = require('yargs').argv;
 const path = require('path');
 const assert = require('assert');
 const chokidar = require('chokidar');
-const debounce = require('lodash.debounce');
+const {debounce} = require('lodash');
 const {getDocJSONPVarNname} = require('./src/shared');
 
 const projectDir = __dirname;
@@ -300,14 +300,11 @@ function writeSingleSchemaPartioned(schema, language, docName, format) {
         const descBasename = `${partKey}.json`;
         const descDestPath = path.resolve(config.releaseDestDir, `${language}/documents/${docName}-parts/${descBasename}`);
         fse.ensureDirSync(path.dirname(descDestPath));
-        const content = JSON.stringify(json, null, 2);
         fse.outputFileSync(
             descDestPath,
-            // format ? JSON.stringify(partDescriptions, null, 2) : JSON.stringify(partDescriptions),
-            content,
+            format ? JSON.stringify(json, null, 2) : JSON.stringify(json),
             'utf-8'
         );
-        // Convnert to JS
         convertToJS(descBasename, descDestPath);
     }
 

build/webpack.config.js

@@ -3,7 +3,6 @@ const VueLoaderPlugin = require('vue-loader/lib/plugin');
 const path = require('path');
 const MiniCssExtractPlugin = require('mini-css-extract-plugin');
 
-
 module.exports = {
     entry: path.resolve(__dirname, '../src/main.js'),
     output: {

editor/src/store/store.js

@@ -1,4 +1,4 @@
-import _ from 'lodash';
+import { cloneDeep, debounce, isEqual }  from 'lodash-es';
 import { socket, socketRequest } from './socket';
 import { Notify } from 'quasar';
 

en/api/echarts.md

@@ -35,7 +35,9 @@ Creates an ECharts instance, and returns an [echartsInstance](~echartsInstance).
     + `devicePixelRatio` Ratio of one physical pixel to the size of one device independent pixels. Browser's `window.devicePixelRatio` is used by default.
     + `renderer`  Supports `'canvas'` or `'svg'`. See [Render by Canvas or SVG](${handbookPath}best-practices/canvas-vs-svg).
     + `ssr` Whether to use server-side rendering. Only available in SVG rendering mode. When enabled, it will no longer render automatically every frame, you have to use the [renderToSVGString](~echartsInstance.renderToSVGString) method to get the rendered SVG string.
-    + `useDirtyRect`  Enable dirty rectangle rendering or not, `false` by default. See [New features in ECharts 5](${handbookPath}basics/release-note/v5-feature).
+    + `useDirtyRect` Enable dirty rectangle rendering or not, `false` by default. See [New features in ECharts 5](${handbookPath}basics/release-note/v5-feature).
+    + `useCoarsePointer` Whether to expand the response area when interacting with elements. `null` means enabling for mobile devices; `true` means always enabling; `false` means always disabling. See [Coarse Pointer](${handbookPath}how-to/interaction/coarse-pointer) for more information.
+    + `pointerSize` Size of expanded interaction size in pixels. It should be used along with `opts.useCoarsePointer`.
     + `width`  Specify width explicitly, in pixel. If setting to `null`/`undefined`/`'auto'`, width of `dom` (instance container) will be used.
     + `height`  Specify height explicitly, in pixel. If setting to `null`/`undefined`/`'auto'`, height of `dom` (instance container) will be used.
     + `locale` Specify the locale. There are two builtins: `'ZH'` and `'EN'`. Or you can use [echarts.registerLocale](~echarts.registerLocale) to register a new locale. Or supported locales can be referenced in [src/i18n](https://github.com/apache/echarts/tree/release/src/i18n).
@@ -263,6 +265,3 @@ Sets the platform-related API, which may need to be provided when non-browser pl
 
 
 {{ use: echarts-graphic }}
-
-
-

en/api/events.md

@@ -235,6 +235,59 @@ Event emitted after range is changed in visualMap.
 }
 ```
 
+## graphroam(Event)
+Event emitted after [series-graph](option.html#series-graph) is roamed.
+
+```ts
+{
+    type: 'graphroam',
+    seriesId: string,
+    zoom: number, // zoom ratio of roaming once
+    originX: number,
+    originY: number
+}
+```
+
+## georoam(Event)
+Event emitted after [geo](option.html#geo) is roamed.
+
+```ts
+{
+    type: 'georoam',
+    componentType: 'geo' | 'series',
+    seriesId: string,
+    zoom: number, // zoom ratio of roaming once
+    originX: number,
+    originY: number
+}
+```
+
+## treeroam(Event)
+Event emitted after [series-tree](option.html#series-tree) is roamed.
+
+`treeroam` events include two types. One is triggered by panning and the parameters are:
+
+```ts
+{
+    type: 'treeroam',
+    seriesId: string,
+    dx: number,
+    dy: number
+}
+```
+
+The other type is triggered by zooming and the parameters are:
+
+```ts
+{
+    type: 'treeroam',
+    seriesId: string,
+    zoom: number, // zoom ratio of roaming once
+    originX: number,
+    originY: number
+}
+```
+
 ## timelinechanged(Event)
 **ACTION:** [timelineChange](~action.timeline.timelineChange)
 Event emitted after time point in timeline is changed.
@@ -463,6 +516,20 @@ chart.on('finished', function () {
 });
 ```
 
+Note that it's recommended to register the callbacks for such an event before `setOption` in case the callbacks may not be called as expected due to the timing issue when the animation is disabled.
+
+```ts
+var option = {
+    // ...
+    animation: false
+    // ...
+};
+chart.on('finished', function () {
+    // ...  
+});
+chart.setOption(option);
+```
+
 
 
 {{ target: event-select }}
@@ -540,4 +607,3 @@ Use `dispatchAction` will trigger this event, but user clicking won't trigger it
     }
 }
 ```
-

en/option/component/tooltip.md

@@ -181,7 +181,7 @@ Whether mouse is allowed to enter the floating layer of tooltip, whose default v
 
 <ExampleUIControlEnum options="html,richText" default="html" />
 
-Render mode for tooltip. By default, it is set to be `'html'` so that extra DOM element is used for tooltip. It can also set to be `'richText'` so that the tooltip will be rendered inside Canvas (SVG rich text is not implemented yet). This is very useful for environments that don't have DOM, such as Wechat applications.
+Render mode for tooltip. By default, it is set to be `'html'` so that extra DOM element is used for tooltip. It can also set to be `'richText'` so that the tooltip will be rendered inside Canvas. This is very useful for environments that don't have DOM, such as Wechat applications.
 
 ## confine(boolean) = false
 
@@ -260,4 +260,3 @@ Conditions to order tooltip. Options:
 + `'valueDesc'`
 
     Base on value, descending order tooltip, only for numberic value.
-

en/option/partial/2d-data.md

@@ -76,7 +76,7 @@ series: [{
 ```
 
 + In [cartesian (grid)](~grid), "dimX" and "dimY" correspond to [xAxis](~xAxis) and [yAxis](~yAxis) respectively.
-+ In [polar](~polar) "dimX" and "dimY" correspond to [radiusAxis](~radiusAxis) 和 [angleAxis](~anbleAxis) respectively.
++ In [polar](~polar) "dimX" and "dimY" correspond to [radiusAxis](~radiusAxis) and [angleAxis](~angleAxis) respectively.
 + Other dimensions are optional, which can be used in other places. For example:
     + [visualMap](~visualMap) can map one or more dimensions to visual (color, symbol size ...).
     + [series.symbolSize](~series.symbolSize) can be set as a callback function, where symbol size can be calculated by values of a certain dimension.
@@ -129,17 +129,17 @@ series: [{
 + When a dimension corresponds to a time axis (type is `'time'`), the value can be:
     + a timestamp, like `1484141700832`, which represents a UTC time.
     + a date string, in one of the formats below:
-        + a subset of [ISO 8601](http://www.ecma-international.org/ecma-262/5.1/#sec-15.9.1.15), only including (all of these are treated as local time unless timezone is specified, which is consistent with [moment](https://momentjs.com/)):
+        + a subset of [ISO 8601](https://www.ecma-international.org/ecma-262/5.1/#sec-15.9.1.15), only including (all of these are treated as local time unless timezone is specified, which is consistent with [moment](https://momentjs.com/)):
             + only part of year/month/date/time are specified: `'2012-03'`, `'2012-03-01'`, `'2012-03-01 05'`, `'2012-03-01 05:06'`.
             + separated by `"T"` or a space: `'2012-03-01T12:22:33.123'`, `'2012-03-01 12:22:33.123'`.
             + timezone specified: `'2012-03-01T12:22:33Z'`, `'2012-03-01T12:22:33+8000'`, `'2012-03-01T12:22:33-05:00'`.
         + other date string format (all of these are treated as local time):
           `'2012'`, `'2012-3-1'`, `'2012/3/1'`, `'2012/03/01'`,
           `'2009/6/12 2:00'`, `'2009/6/12 2:05:08'`, `'2009/6/12 2:05:08.123'`.
     + a JavaScript Date instance created by user:
-        + Caution, when using a data string to create a Date instance, [browser differences and inconsistencies](http://dygraphs.com/date-formats.html) should be considered.
+        + Caution, when using a data string to create a Date instance, [browser differences and inconsistencies](https://dygraphs.com/date-formats.html) should be considered.
         + For example: In chrome, `new Date('2012-01-01')` is treated as a Jan 1st 2012 in UTC, while `new Date('2012-1-1')` and `new Date('2012/01/01')` are treated as Jan 1st 2012 in local timezone. In safari `new Date('2012-1-1')` is not supported.
-        + So if you intent to perform `new Date(dateString)`, it is strongly recommended to use a time parse library (e.g., [moment](https://momentjs.com/)), or use `echarts.number.parseDate`, or check [this](http://dygraphs.com/date-formats.html).
+        + So if you intent to perform `new Date(dateString)`, it is strongly recommended to use a time parse library (e.g., [moment](https://momentjs.com/)), or use `echarts.number.parseDate`, or check [this](https://dygraphs.com/date-formats.html).