You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: