VisualMap support unboundedRange #21113
Merged
+107
−5
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.
Brief Information
This pull request is in the type of:
What does this PR do?
This is a follow-up of #21104 .
An new option is introduced:
unboundedRange
: Whether to treat the range as unbounded whenrange
touchesmin
ormax
.true
:when
range[0]
<=min
, the actual range becomes[-Infinity, range[1]]
;when
range[1]
>=max
, the actual range becomes[range[0], Infinity]
.NOTE:
- This provides a way to ensure all data can be considered in-range when
min
/max
are not precisely known.
- Default is
true
for backward compatibility.- Piecewise VisualMap does not need it, since it can define unbounded range in each piece,
such as "< 12", ">= 300".
false
:Disable the unbounded range behavior.
Use case:
min
/max
reflect the normal data range, and some outlier data should always betreated as out of range.
Doc
apapche/echarts-doc commit: db69b8cef0d627a62f360757926e659022a4b483