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: use precision defaults only when markline type is average #15324

Conversation

Map1en
Copy link
Member

@Map1en Map1en commented Jul 9, 2021

Brief Information

This pull request is in the type of:

  • bug fixing
  • new feature
  • others

What does this PR do?

fix: rm default val of precision and calc val automatically

Fixed issues

close #15247

Details

Before: What was the problem?

The max and min markline should not follow the precision option

After: How is it fixed in this PR?

Use precision defaults only when markline type is average

Misc

  • The API has been changed (apache/echarts-doc#xxx).
  • This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs

NA.

Others

Merging options

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

Other information

@echarts-bot
Copy link

echarts-bot bot commented Jul 9, 2021

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.

@pissang pissang added this to the 5.2 milestone Jul 9, 2021
@Map1en Map1en changed the title fix: rm default val of precision and calc val automatically fix: use precision defaults only when markline type is average Jul 10, 2021
@DanielBogenrieder
Copy link

Any news on this one, or any reason this was never merged? We just ran into this issue and it feels strange that the default precision of 2 is applied here. Happy to pick up the PR and rebase it if we agree that this will be changed :)

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.

The max and min markline should not follow the precision option
3 participants