Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(polar): fix unexpected clipping in polar coordinate #20370

Merged
merged 3 commits into from
Sep 26, 2024

Conversation

sz-p
Copy link
Contributor

@sz-p sz-p commented Sep 24, 2024

Brief Information

This pull request is in the type of:

  • bug fixing
  • new feature
  • others

What does this PR do?

Fixed issues

#20363

Details

Before: What was the problem?

The maximum value symbol in polar coordinate system scatter chart of radiusAxis is not displayed

After: How does it behave after the fixing?

Display the symbol

Document Info

One of the following should be checked.

  • This PR doesn't relate to document changes
  • The document should be updated later
  • The document changes have been made in apache/echarts-doc#xxx

Misc

ZRender Changes

  • This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs

N.A.

Others

Merging options

  • Please squash the commits into a single one when merging.

Other information

Copy link

echarts-bot bot commented Sep 24, 2024

Thanks for your contribution!
The community will review it ASAP. In the meanwhile, please checkout the coding standard and Wiki about How to make a pull request.

Copy link
Contributor

github-actions bot commented Sep 25, 2024

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

const r = this.r;
const r0 = this.r0;

return d2 <= r * r && d2 >= r0 * r0;
// minus a tiny value 1e-4 in double side to avoid being clipped unexpectedly
return (d2 - 1e-4) <= r * r && (d2 + 1e-4) >= r0 * r0;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please consider the scenario where r is equal to r0, in which case the data within the polar coordinates should consistently be clipped. Therefore, I recommend adding r !== r0 && as a safeguard. Additionally, to minimize redundancy, we may define a constant const epsilon = 1e-4;.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK got this. I will do this tody

@Ovilia Ovilia merged commit 38613d2 into apache:master Sep 26, 2024
2 checks passed
Copy link

echarts-bot bot commented Sep 26, 2024

Congratulations! Your PR has been merged. Thanks for your contribution! 👍

@Ovilia Ovilia added this to the 5.5.2 milestone Sep 26, 2024
@Ovilia
Copy link
Contributor

Ovilia commented Sep 26, 2024

We sincerely appreciate your valuable contributions! We are currently running a special promotion for users who submit a Pull Request between September 25, 2024, and December 31, 2024. Eligible participants will receive a two-year enterprise membership to Baidu Comate, valued at 2000 RMB (approximately 285 USD).

To learn more about this product, please visit https://comate.baidu.com/. If you are interested in this offer, kindly send an email with the link to your Pull Request along with your Comate username and email address to [email protected] to claim your membership.

Thank you once again for your support!

@plainheart plainheart changed the title Fix 20363 fix(polar): fix unexpected clipping in polar coordinate Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants