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

does this library function on d3 vs 3.5.15 vs 3.5.17 ? #32

Closed
msusol opened this issue Feb 18, 2017 · 2 comments
Closed

does this library function on d3 vs 3.5.15 vs 3.5.17 ? #32

msusol opened this issue Feb 18, 2017 · 2 comments

Comments

@msusol
Copy link

msusol commented Feb 18, 2017

My company has an internal third_party library for R packages, and wants me to use existing d3.min.js in third_party that is only versioned to 3.5.15. Due to d3 v3 deprecation, they will not want me to update to 3.5.17 for offline use in d3r package that sunburstR relies on.

Is there a critical issue if I were to use 3.5.15 instead of 3.5.17?

@timelyportfolio
Copy link
Owner

No, I do not think there will be any problem whatsoever using 3.5.15. At one point, I considered allowing any verson in d3r, but size becomes a problem especially with CRAN. Let me know if you need any pointers on ways of accomplishing this.

@cjyetman
Copy link
Collaborator

this is probably irrelevant now that sunburstR has been converted to D3v4?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants