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
After converting to d3v4, I would like to modularize the JS code to resemble Let's Make a D3 Plugin. As an example of this, I have done d3horizonR. d3horizonR is not perfect, but demonstrates how the JS lives in its own separate directory ignored by the R pkg. The JS gets processed, built, and compiled and then moves to the inst/htmlwidgets folder for use by the R package. The advantage is we can stick to a "modern" typical JS build and test workflow.
After converting to
d3v4
, I would like to modularize the JS code to resemble Let's Make a D3 Plugin. As an example of this, I have doned3horizonR
.d3horizonR
is not perfect, but demonstrates how the JS lives in its own separate directory ignored by the R pkg. The JS gets processed, built, and compiled and then moves to theinst/htmlwidgets
folder for use by the R package. The advantage is we can stick to a "modern" typical JS build and test workflow.See
leaflet
as another example.Potential Modules
A quick round of code analysis reveals some clear module opportunities.
The text was updated successfully, but these errors were encountered: