Skip to content

Conversation

100pah
Copy link
Member

@100pah 100pah commented Jul 17, 2025

Brief Information

This pull request is in the type of:

  • bug fixing
  • new feature
  • others

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 when range touches min or max.

  • 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 be
    treated as out of range.

Doc

apapche/echarts-doc commit: db69b8cef0d627a62f360757926e659022a4b483

Copy link
Contributor

github-actions bot commented Jul 17, 2025

The changes brought by this PR can be previewed at: https://echarts.apache.org/examples/editor?version=PR-21113@b5e8e81

@Ovilia Ovilia merged commit ad86b5a into master Jul 17, 2025
2 checks passed
@Ovilia Ovilia deleted the fix/visualMap-range branch July 17, 2025 12:17
@Ovilia Ovilia added this to the 6.0.0 milestone Jul 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants