Repository navigation
docs(api): clarify dataZoom value ranges in getOption - #542
Closed
Narek-Khachikyan wants to merge 1 commit into
Closed
Narek-Khachikyan wants to merge 1 commit into
Narek-Khachikyan wants to merge 1 commit into
Conversation
Companion to apache/echarts#21827 for apache/echarts#21408. The documentation text was generated by AI.
3 of 9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
getOption()can return an accepted value-mode dataZoom input that differs from a visible axis limit. The API docs need to explain that output so callers can interpret recovered options correctly.This is the documentation companion to apache/echarts#21827 for apache/echarts#21408.
The English and Chinese pages distinguish accepted input from each axis's calculated window, with the same example using
startValue: -200andendValue: 200. Both explain null percentages, unspecified value inputs, calculated percentage-mode pairs and effective range modes after actions. Existing recovery and partial-update guidance stays intact. No new API or option is added.Validation
The repository parser passed the complete English and Chinese API and option trees. Checks covered the generated
getOptioncontent and the actualdataZoom-inside.rangeModelink target. The diff adds eight lines across two API pages and preserves their original line endings.No full site build or browser layout check was run.
This description and the documentation text were generated by AI.