-
Notifications
You must be signed in to change notification settings - Fork 19.6k
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(marker): markArea
of bar series now covers whole specified categories
#17098
Conversation
Thanks for your contribution! |
Any plans to merge this pr? |
@dynamikus Thanks for your contribution and please be patient to wait for reviews since we are mostly working part-time on the project. :) |
This PR looks awesome! I would like to see more test cases, for example, when |
@jiawulin001 |
@Ovilia More test cases are on the way.
@dynamikus Thank you for your applause, and it's totally fine to ask. I am really glad if my work can help someone else. |
@Ovilia A new test case in the same html is added |
@jiawulin001 Thanks! Please also run the visual test for all cases and see if there are diffs that we should be aware of. You should compare local changes with the nightly build of master branch. |
@Ovilia Thank you for guiding me to visual test. However since "Run all test" takes forever to run, I run the test relative to Update 2022/6/13 11:28Seems that there are issues of Update 2022/6/13 11:39Issue resolved, now most visual test passed. Let me know if I need to do other testcases. Also it's very time consuming to run all visual tests. It takes 40+ minutes to execute all of them. Is there a way to solve or improve this? |
@jiawulin001 Thanks for running the visual tests! I think you are working with the unexpected test results, right?
Usually, we only do a thorough test before releasing a new version or the PR changes a lot of logic or the reviewers are not very confident with the changes. For PRs like this, test the files that contain "mark" in their names should be enough. But a thorough test is always helpful so thanks for the effort and time! :) |
If you mean the issues of |
Hi @jiawulin001, Thanks for your recent contributions! They help a lot! It would be better if you could check the reason why the configured |
My apologies for those lint fix commits! I've been using github desktop to submit commits and the hooks seem not to work on it. I'll use my IDE to submit commits and make sure I execute lint scripts before them in the future. Thank you for your reminding! |
I have another question regarding visual test. When I am doing all kinds of PR, is there a criterion how I pick what visual tests to do and how should I present the results to the community? |
If you want to export the report, there's a "ALL RUNS" button on the menu. Check the versions and time to know which running should be exported and click "report" to export. |
Any update on this PR? Would help a lot as neither markArea or splitArea is working correctly today in bar charts with dataZoom :( |
@Ovilia Hi, I think I've resolved the conflict in merging. Any other suggestions on how should I improve this PR? Or should we move forward to merging? |
Hi, Is there any plan to merge the problem to the latest version in the near future? @Ovilia 🤔️ |
This PR is scheduled in 5.4.1, which should be published in November. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've run with all test cases and it looks fine.
To reviewers: If this PR is going to be described in the changelog in the future release, please make sure this PR has one of the following labels: This message is shown because the PR description doesn't contain the document related template. |
Congratulations! Your PR has been merged. Thanks for your contribution! 👍 |
markArea
of bar series now covers whole specified categories
It seems this PR breaks zoom functionality: #18099 |
Since version 5.4.1 the markArea in my bar chart is broken, I think it's related to this PR |
@ily-salamat Hi, thanks for your report! Please create a new issue and make a reference to this PR. We'll try to confirm and fix it in v5.5.0. |
Also, thank you @andrius-kurtinaitis for filing a similar bug. I've marked your issue as high-priority and will fix it first. |
Brief Information
This pull request is in the type of:
What does this PR do?
MarkArea in
bar series/category axis
now covers the categories specified rather than area between bars of specified categories.Fixed issues
Details
Before: What was the problem?
MarkArea in
barSeries/category-axis
is marking the area between bars of category specified, which is not wanted in category axis chart.After: How is it fixed in this PR?
Now markArea marks the whole category zones specified. Multi-bars and invert input are both considered.
Left MarkArea
Left MarkArea
Misc
Related test cases or examples to use the new APIs
bar-markArea.html
Others
Merging options
Other information