Converting R data.frame
objects to/from JavaScript objects
#364
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on #363.
Constructing new R objects now supports input objects of the form:
{a: [...], b: [...]}
or D3-style data arrays of the form:[{a: ..., b: ...}, {a: ..., b: ...}, {a: ..., b: ...}, ... ]
Where possible (columns are all atomic vectors, all of equal length, and of consistent types), lists are constructed with class
data.frame
when constructed usingawait new RObject()
.Direct construction with
RList()
does not create adata.frame
.R
data.frame
objects may be converted into D3-style data arrays using the new R list object method.toD3()
.Update docs to give more information about conversion of R and JavaScript objects.
Fixes #303.