-
Notifications
You must be signed in to change notification settings - Fork 525
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
Axis Prop Updates #1835
Axis Prop Updates #1835
Conversation
@boygirl Seems like this was a very simple fix. Suspiciously simple. But I couldn't find any unintended consequences of fixing it like this. Any insights on your end? |
I looked into what you mentioned about offsetX and offsetY on Chart and Axis, but that didn't seem to be related as far as I could tell. |
@jhumbug apologies! I think this does fix a portion of the issue, but I should have been clearer about the axis offset issue. Here's a gif that I think illustrates the problem: In the chart above, there are not user provided |
Ok, yeh I missed that. I will look into that part of it now, thank you for the gif. |
541f4e2
to
10ca857
Compare
From looking at the stories, it looks like there's a systematic problem with horizontal charts and with how the range / padding is being calculated |
Yep, addressing those now. Most are the horizontal issue which is easy. I'll look at range/padding after. |
Got most of the chromatic issues with those fixes. I'll work on the few left tomorrow. |
The last chromatic changes are from added/changed tests in previous PRs and 2 (VictoryScatter: Theme & VictoryLine: Theme) that actually look correct now, rather than the previous version. They have slight differences in the grid position, but it looks like the new versions are right now, no? |
@jhumbug A couple minor comments, but this is otherwise looking ready. And axes look so much nicer when zooming |
This provides a fix for when the domain of a dataset using VictoryZoom changes, such as switching out data on demand.