balasahebbagal opened a new issue, #19522: URL: https://github.com/apache/echarts/issues/19522
### What problem does this feature solve? I have observed a limitation in E-charts when it comes to plotting graphs with multiple Y-axes. particularly concerning the 'splitNumber' parameter. As of the current implementation, E-charts allows users to plot graphs with multiple Y-axes using the 'yAxis' configuration, where each object within the array represents a distinct Y-axis. The 'splitNumber' key within these objects defines the number of divisions on the Y-axis and their corresponding labels based on the maximum data value. The observed problem arises when configuring 'splitNumber' for multiple Y-axes. While users have the flexibility to specify 'splitNumber' for each Y-axis individually, E-charts currently applies the 'splitNumber' only to the first Y-axis. Subsequent Y-axes inherit the 'splitNumber' from the first one, leading to incorrect axis point calculations. For example, if the 'splitNumber' for the first Y-axis is set to 5, and the second Y-axis has a 'splitNumber' of 3, the expectation is to have three points with intervals based on the maximum value of the data. However, the current behavior results in five points on the second Y-axis, inherited from the first one. This limitation affects the accurate representation of data, especially when different Y-axes require distinct 'splitNumber' configurations. To address this issue, I kindly request the implementation of independent 'splitNumber' support for each Y-axis, ensuring that the specified values are applied correctly to their respective axes. By addressing this concern, E-charts can enhance its flexibility and provide users with more accurate and customizable visualizations, particularly in scenarios involving multiple Y-axes with varied 'splitNumber' requirements. ### What does the proposed API look like? If the splitNumber issue is fixed in E-charts, it would result in more accurate and customizable visualizations, especially in scenarios involving multiple Y-axes with varied splitNumber requirements. Here are the potential positive outcomes of fixing this issue: 1. Independent Configuration: Users would be able to independently configure the splitNumber for each Y-axis. This means that different Y-axes can have their own distinct splitNumber values, allowing for more precise control over the number of divisions and their intervals. 2. Accurate Axis Points: Each Y-axis would accurately represent the specified splitNumber, ensuring that the axis points are correctly calculated based on the maximum data value for that specific axis. This would eliminate the current behavior where subsequent Y-axes inherit splitNumber values from the first one.. 3. Customizable Visualizations: Users would have greater flexibility in creating visualizations that meet their specific requirements. Whether dealing with multiple datasets or diverse scales of data, the ability to set independent splitNumber values for each Y-axis enhances the customization options available to users. 4. Improved Data Representation: The fixed splitNumber issue would result in more meaningful and contextually relevant representations of data on each Y-axis. This is particularly important when dealing with datasets that have distinct characteristics or scales across different Y-axes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@echarts.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@echarts.apache.org For additional commands, e-mail: commits-h...@echarts.apache.org
