ryancui92/echarts-composables

Using ECharts in composable way

echarts-composables's Issues

make more examples on docs

1. write a documentation markdown inside the repo, using git's vcs to keep different versions docs
2. keep only playground, no need for vitepress docs

a toy playground

1. use pre-defined mock data or upload your own data or from API
2. define the dimensions, metrics, meta, addons on visualized interface (dnd)
3. code generated

Support basic series type

• scatter
• effectScatter
• treemap
• sunburst
• heatmap
• graph
• sankey

支持 useBarStack 柱状图堆叠

Support multiple keys in metric and dimension definitions

Currently, when we want to declare multiple Bar metrics, we have:

const metrics = [
  {
    key: 'data1',
    visual: MetricType.Bar,
  },
  {
    key: 'data2',
    visual: MetricType.Bar,
  },
  {
    key: 'data3',
    visual: MetricType.Bar,
  },
]

It's a bit long-winded, so we introduce multiple key definitions:

const metrics = [
  {
    key: ['data1', 'data2', 'data3'],
    visual: MetricType.Bar,
  }
]

Same in dimension, which can accepted multiple key in some specific dimension type, like DimensionType.Series

const dimensions = [
  {
    key: ['type', 'time'],
    visual: DimensionType.Series,
  }
]

The case would generate a combined dimension from type and time as type-time. All datum would be joined with -.

The feature would be released with new major version.

radar metric should include max option in radar.indicator

The metric should align to a same max value.

Addons should be implemented inside the main function

Remove UniversalAddon. All add-on should be a combined config instead, they should have the least overlap with each other.
It should be easy to add a new add-on in Type-Safe way.

split CategoryAxis into XAxis and YAxis

CategoryAxis is vague and useYAxisAsDimension is not intuitive. Since we don't usually 'rotate' the gragh once the requirement is determined, so the dimension axis should be set up earlier.

We decide to introduce DimensionType.XAxis and DimensionType.YAxis to let user determine how a graph should be show instead of assuming xAxis is dimension axis and then apply a hook to 'rotate' it. It would be much easier to understand and to implement too.

CategoryAxis would be preserved but labeled as deprecated, same to useYAxisAsDimension hook. The features would be released as a new major version.

umd format support

Provide a link to umd format js file.