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

[Bug] Circle line lost when boundary gap false in the stack bar on polar chart #20172

Closed
jieun94 opened this issue Jul 18, 2024 · 1 comment
Closed

Comments

@jieun94
Copy link

jieun94 commented Jul 18, 2024

Version

5.5.1

Link to Minimal Reproduction

https://codepen.io/jieun94/pen/xxoZXrX

Steps to Reproduce

  1. Enter the wind direction value of length 16 in the category to indicate 16 orientation
  2. False the boundary gap to position the north in the 0 degree direction

Current Behavior

The line between the last category and the first category is lost.

Expected Behavior

The line between the last category and the first category is connected to form a circle.

Environment

- OS: window 11 
- Browser: Chrome/124.0.0.0
- Framework : vue3

Any additional comments?

No response

@jieun94 jieun94 added the bug label Jul 18, 2024
@plainheart plainheart added the pending We are not sure about whether this is a bug/new feature. label Jul 18, 2024
@Ovilia Ovilia added topic: polar and removed pending We are not sure about whether this is a bug/new feature. labels Jul 18, 2024
@Ovilia Ovilia self-assigned this Jul 18, 2024
@Ovilia
Copy link
Contributor

Ovilia commented Jul 19, 2024

After digging into the code, I found this is not-a-bug. In fact, this is the result of intentionally adjusted so that bars don't get mixed. For example, if we have the following data with boundaryGap: false without adjusting

{
    type: 'bar',
    data: [10, 20, 30, 40],
    coordinateSystem: 'polar',
    itemStyle: {
        opacity: 0.5
    }
}

The first data is overlapped with the last data.

image

To avoid this, this commit introduced a way to adjust the range according to data count.

And here is why we cannot just change the axisLine and axisSplitLine to become a circle: it's logically not consistant when it's slightly not match a circle. So the result of https://codepen.io/jieun94/pen/xxoZXrX should be regarded as by design, although it may seem to be unexpected at the first sight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants