-
Notifications
You must be signed in to change notification settings - Fork 33
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
hideAxis is recently broken #57
Comments
@joshhjacobson thanks so much for the report. I have a fix for this, but I'm going to look quickly at #26 to see if we can resolve both. |
timelyportfolio
added a commit
to timelyportfolio/parcoords-es
that referenced
this issue
Jan 1, 2019
@timelyportfolio thank you for the fast response, so glad you were able to figure this out so quickly! |
BigFatDog
added a commit
that referenced
this issue
Jan 9, 2019
Thanks @joshhjacobson for discovering this potential bug and @timelyportfolio 's quick fix on his weekend! v2.2.5 has been released to deliver to fix. |
joshhjacobson
added a commit
to joshhjacobson/parcoords-es
that referenced
this issue
Jan 18, 2019
BigFatDog
added a commit
that referenced
this issue
Jan 30, 2019
fix lingering issues from #57 following @timelyportfolio's approach
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In version 2.2.0, the bug fix in the
brushFor
function had the side effect of partially breakinghideAxis
. The function works when data is first added to the chart, but if called individually there is an error. The following, taken from thebrushing.html
demo, demonstrates the issue:This gives:
In versions prior to 2.2.0, this was not an issue. Now, it seems that the
axis
being referenced inbrushFor.js
herehas already been removed from
config.dimensions
insideEffects.js
herethus,
config.dimensions[axis]
is undefined.I would attempt to fix this myself, but I'm not really sure why it's happening. @timelyportfolio do you have any thoughts on this? Maybe we could delay execution of
pc.dimensions(without(config.dimensions, d.value))
until afterbrushFor
has been executed?The text was updated successfully, but these errors were encountered: