-
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
Victory 2298 Tooltip Bug Fix #3027
Open
ryansrofe
wants to merge
4
commits into
main
Choose a base branch
from
bug/2298/y0-prop-inside-voronoi
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The issue is in the getDatasets method where the voronoi points are calculated. Currently, it calculates the voronoi point position as the midpoint between x and x0 for X coordinates, and y and y0 for Y coordinates. The fix should be to use just the primary coordinates for voronoi calculations, ignoring the baseline coordinates.
Added a Voronoi section to Storybook to test the users bug example (voronoi-y0). I also added all the existing Voronoi examples to Storybook from the docs.
🦋 Changeset detectedLatest commit: 9a50fc5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 30 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
nlkluth
approved these changes
Jan 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The problem occurs in
voronoi-helpers.ts
when calculating points for tooltips withy0
values. The issue is in the getDatasets method where the voronoi points are calculated. Currently, it calculates the voronoi point position as the midpoint betweenx
andx0
for X coordinates, andy
andy0
for Y coordinates.This is problematic because for area charts using
y0
, the tooltip should activate based on the top line of the area (they
value), not the midpoint betweeny
andy0
. The current implementation causes tooltips to activate at points that are visually far from where users would expect them to be. This fix uses only the primary coordinates for voronoi calculations, ignoring the baseline coordinates.This would make the tooltips activate based on proximity to the actual data points rather than the midpoint between the top and bottom of areas, which is what users are expecting.
Fixes #2298
Type of Change
How Has This Been Tested?
I added the reporting user's code that includes the bug to Storybook and tested it in Storybook. Without this change the code produces the bug as described, with this change the bug is no longer present.
Checklist