-
Notifications
You must be signed in to change notification settings - Fork 207
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
d3 v4 #211
Comments
Yep, it will be messy. |
Hmm. Yeah, this will be messy. Let us talk to figure out what we can potentially do. |
So, I just realized that people developing on d3 v4.0 are more likely to use ES6 and build custom bundles of the d3 modules and their application code. If not, we can encourage them to do so. This way, the bundle will be standalone and will not pollute the namespace and hence these widgets can co-exist with d3 v3.0. I have a widget built using d3 v4.0 that is close to completion and I can use that to test this. |
I'm writing a reusable charting
System detailssetting value
|
@mortonanalytics, this is a RStudio Viewer issue. I would recommend using babel to transpile. If you want to stay within |
RStudio 1.2 should resolve this (the underlying browser engine will switch from an old WebKit fork to something Chromium based) but it's quite a few months away from being ready for release, much less the predominant version. |
I just found out the just released d3 v4.0 isn't backward compatible with older versions of d3. I don't know how we can compose widgets that use both on the same page.
The text was updated successfully, but these errors were encountered: