[Discussion] Apache ECharts 6.0 Feature Discussion

[Ovilia]

Apache ECharts 5.0 was released in December 2020, and now it's time for the next major version: 6.0!

We are excited to announce that we plan to release Apache ECharts 6.0 in the first quarter of 2025. We have put together a list of features that we intend to include in this upcoming release.

We would love to hear from you about which features you are most excited about and looking forward to using. Please share your thoughts and let us know what you think!

It's important to keep in mind that most of our contributors work on ECharts in their free time, so some features may take longer to implement than others. If you are passionate about a particular feature and would like to help us bring it to life, we warmly welcome you to join our community and contribute to the development of ECharts 6.0!

[DanielBogenrieder]

Great to hear and see the amazing progress.
For us most important would be to get this issue here solved:
#16825 -> There is already a PR and it is really sad to look at these amazing charts and seeing the overlap most of the time.
Less important but would be nice to see it merged at some point: #17579 (comment)
Other issues we would profit from are:
#16744 (comment)
#13759 (comment)

I appreciate the great work you are all doing and happy to contribute further if we see progress on the things we already contributed.

Greetings,
Daniel

[Ovilia]

@DanielBogenrieder Thank you guys for submitting such excellent pull requests! I apologize if I miss any updates due to the volume of messages; it can sometimes be a bit overwhelming. However, I assure you that I will review these requests soon. :)

[Time-coding]

I hope this feature can be added： #18157，thanks！

[Ovilia]

I hope this feature can be added： #18157，thanks！

I saw that you made some attempts to implement this feature. How about making it to be a pull request?

[AAravind27]

Those are some great features you have on list. Would it be possible to revisit #19182 ? Thanks!

[LofiSu]

请问echarts有交流群吗

[zpinocchio]

Could you add a sizeMap similar to the visualMap component to map sizes? For example, would it be more intuitive to use a sizeMap for the legend of the point sizes in the bubble plot?

[ianzone]

There could be a react component version.

[AidMen]

I would really like to see the hierarchical/grouped bar chart like mentioned in these issues: #4902 #13839 #18923 #19441
Unfortunately three of those issues don't seem to be posted as feature requests, but I think the use case is quite common as I also needed it for one of my projects that use Apache ECharts.

[helgasoft]

I think fixing the tree collapse problem is long overdue: PR #18491 for #17266 and others.
Tree has now another serious one #20136.

[mohsenomidi]

It would be exciting to have a reactjs component officially

[mohsenomidi]

Organization and position tree chart is very useful the Issue 9405 - Requested 6 years ago

[jdgme]

An enhancement that I think would be pretty simple and quick to implement is #20200.

A bit more effort would be involved in a longstanding issue that I commented on in 2022:

#15585 (comment)

I do see that #15585 has been slated for 6.0 and is in the backlog.

[andregamma]

We need to have a better way to apply number formatters globally. Some languages don't format numbers as in English, and it is too much work to replace the default formatter in all components.

This issue has been reported in some issues already: #8294 #4180

I think we have some ways to achieve that:

• Have per-locale configurations and make the addCommas function use that as a source
• Global user-provided formatter function
• Use Intl.FormatNumber or .toLocaleString() using the current echarts locale

The locale files already have some configuration for thousand separators, at first I thought it was used for number formatters but seems that is not the case.

[Ovilia]

Could you add a sizeMap similar to the visualMap component to map sizes? For example, would it be more intuitive to use a sizeMap for the legend of the point sizes in the bubble plot?

This sounds to be an interesting feature. One challenge may be, what happens if some of the bubble sizes are to large to be displayed in the legend.

[Ovilia]

@andregamma There is a valueFormatter option. Do you think this may save the problems you mentioned?

[amirajv]

Thank you echarts team. Excited for the new version.

I think another very useful feature is #13645 / #17504

[juliepagano]

It'd be great to see #16099 (better support for time-based bar chart binning).

[jonoshearman]

Hello, thank you team for all the hard work - ECharts 5 made some huge progress and I look forward to v6!

for v6 I would personally love to see an official schema for all the JSON options available.
#16427 has already been requested.
I think it's common to generate the ECharts JSON from a backend service - in java/python/.NET/etc, and it would be awesome to have a common schema to be able to generate against. There are already projects for specific languages linked in the docs, eg Echarts-Java or Pyecharts, but sometimes they get left unmaintained.

Other than that - I would support the design token idea proposed by @Ovilia in #20202 and any other ways to simplify changing similar settings across multiple series types etc.
There are a lot of options available (a great thing) but sometimes the interface to find/change them is challenging.

thanks again!

[makepanic]

Thanks for working on ECharts.

#19941 would be nice to have. I was looking at improving a single axis scatter plot with inspiration from https://nightingaledvs.com/ive-stopped-using-box-plots-should-you/ but it seems like jittering the scatter points is currently not possible.

Nevermind it seems like that PR is already tagged for 6.0 😄

[hitao123]

请问echarts有交流群吗，qq 群或者微信群

[yuicer]

noticed that echarts 5 already have some excited changes like datasets, visualMap, series. still, I think we can go father in version 6

1. could we really have a visual scale to replace {visualmap.show:false}, scale of grammar of graphics is useful for some situation, it can convergence config option and make more possibility. and still, can we rethink xAxis/yAxis. it mixed axes style, value scale, data source. not so friendly for users
2. datasets group filter is very useful, cause we do need a new way to quickly set multi series
3. option.grid is very important for charts facet, could we optimize help doc or demo?

@Ovilia
thx for all amazing works

[ptandler]

It's so cool to hear that you work on a new major version - many thanks already! ❤️ 🙏

One - actually quite small but very helpful - feature I really miss and would like to suggest for 6.0 is adding a time zone config option per time axis (see #14453). In case you display data in different time zones, this would be really helpful.

[electroheadfx]

Maybe fix too the label z-index with lots data ?

I re-open the issue because I did a reproducible project with this issue, it seem it happen when there is too much data. I put a multiplier in line #1, when multiplier = 1 it works:
echarts multiplier data = 1

When multiplier is 2, it double the data, the z index in label issue happen:
echarts multiplier data = 2