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

version 1.2 passes wrong values into range() call #30

Closed
mrjones-plip opened this issue Sep 21, 2016 · 0 comments
Closed

version 1.2 passes wrong values into range() call #30

mrjones-plip opened this issue Sep 21, 2016 · 0 comments
Labels

Comments

@mrjones-plip
Copy link
Contributor

on line 459 we need to use {{minValue}} and {{{maxValue}} instead of {{attrValue.maxNegative}} and {{attrValue.minNegative}}. If we don't, then d3 complains it's being passed invalid values:

{{Unexpected value maxValue parsing r attribute.}}

mrjones-plip pushed a commit that referenced this issue Sep 21, 2016
mrjones-plip pushed a commit that referenced this issue Sep 21, 2016
mrjones-plip pushed a commit that referenced this issue Sep 21, 2016
mrjones-plip pushed a commit that referenced this issue Sep 21, 2016
mrjones-plip pushed a commit that referenced this issue Sep 21, 2016
mrjones-plip pushed a commit that referenced this issue Sep 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant