- 25 9月, 2020 2 次提交
- 24 9月, 2020 4 次提交
- 23 9月, 2020 7 次提交
- 22 9月, 2020 1 次提交
-
-
由 saniac 提交于
-
- 18 9月, 2020 2 次提交
- 17 9月, 2020 2 次提交
- 07 9月, 2020 1 次提交
-
-
由 100pah 提交于
ts: (1) add more strict type check for id, name from option. (2) add more strict conversion for id, name from option.
-
- 25 8月, 2020 1 次提交
-
-
由 100pah 提交于
(1) fix data-transform specify dimension by index throw error. (2) some little refactor about source creation original brought by feature data transform.
-
- 12 8月, 2020 1 次提交
-
-
由 100pah 提交于
fix: [data-transform] Make the comparison operation accurate in common edge cases. Support parser 'number'.
-
- 31 7月, 2020 1 次提交
-
-
由 100pah 提交于
-
- 29 7月, 2020 1 次提交
-
-
由 susiwen8 提交于
-
- 28 7月, 2020 1 次提交
-
-
由 pissang 提交于
-
- 27 7月, 2020 1 次提交
-
-
由 pissang 提交于
-
- 26 7月, 2020 1 次提交
-
-
由 100pah 提交于
-
- 19 7月, 2020 1 次提交
-
-
由 pissang 提交于
-
- 19 6月, 2020 2 次提交
-
-
由 100pah 提交于
-
由 100pah 提交于
(1) The "scale extent calculation" is depended by both coord sys and "dataZoom". So it need to be performed in different stage of workflow and should avoid to call it repleatly or implement it repeatly. But previously, the "scale extent calculation" is implemented both in `axisHelper.ts` and `dataZoom/AxisProxy.ts`, where different code implements similar logic. "Scale extent calculation" is based on input of: (I) option specified min/max/scale (including callback) and (II) dataExtent and (III) some filter related components like dataZoom. Currently we need add more filters depends on that axis scale calculation. e.g., (I) one axis min max effect the other axis extent (II) custom filter. So we refactor that "Scale extent calculation" as a reusable module (see `scaleRawExtentInfo.ts`). (2) Based on (1), make the callback of axis.min/axis.max consistent whatever it is called in "data processing stage" or "coord sys updating stage" (3) Based on (1), fix some "inconsistent" flaw in dataZoom when handling stacked series. (4) Fix the type of axis.min/max to `ScaleDataValue`. And enable the callback of axis.min/max to return `ScaleDataValue`. (5) Remove some code that never used. (6) Make the "data filter", which will "block stream", not as the default data processor in the register API.
-
- 26 5月, 2020 1 次提交
-
-
由 pissang 提交于
-
- 26 4月, 2020 1 次提交
-
-
由 100pah 提交于
-
- 15 4月, 2020 2 次提交
- 14 4月, 2020 1 次提交
-
-
由 pissang 提交于
-
- 02 4月, 2020 1 次提交
-
-
由 pissang 提交于
-
- 01 4月, 2020 1 次提交
-
-
由 pissang 提交于
-
- 27 3月, 2020 1 次提交
-
-
由 100pah 提交于
-
- 21 3月, 2020 2 次提交
-
-
由 100pah 提交于
And add rule "no-var" to eslintrc
-
由 100pah 提交于
Use eslint rule to check the diff between var and let: "no-use-before-define": "off" "@typescript-eslint/no-use-before-define": 2 no-redeclare: 2 block-scoped-var: 2 no-loop-func: 2 (2) By the way add some eslint rule and unify some code style.
-
- 14 3月, 2020 1 次提交
-
-
由 pissang 提交于
-