-
Notifications
You must be signed in to change notification settings - Fork 6
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
Ticks map using tick.position #437
Comments
The stack trace shows that the error happens with |
It seems to be always the axis for which the min and max value is the same, and disappear if there is This line could be adding too many Ticks. The problem seems to disappear with:
|
It seems that the warning happens if the data is modified while the live server is running (if it is started from scratch with it, there is no error. Maybe you can test that.) The same thing seems to happen if a click button is allowed to change the data:
And the source. |
OK I see, thank you for the reproducible example. The bug is in https://github.com/zakodium-oss/react-d3-utils/blob/6bdf5d6c3983973352bc4a27c72332398cbda5f6/src/hooks/useLinearPrimaryTicks.ts#L27-L39 (we apply the new scale to old ticks from the state). Working on a fix... |
Oh, I see. It makes more sense now. You are welcome. |
Edit: this is just a warning in the console but may be possible to fix?
Example
There should not be x:0 repeated but this would be common when having multiple possible axis combinations:
Error seems to come from this line. where the
getPositions
takes anx
value to make the ticks (it seems so.)Console Log
This is the text error from the console:
The text was updated successfully, but these errors were encountered: