-
Notifications
You must be signed in to change notification settings - Fork 40
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
toJSON(auto_unbox=TRUE, force=TRUE) should not unbox objects wrapped in I() #78
Comments
+1 I like the datatable(iris, options = list(order = list(
list(jsonlite::unbox(1), jsonlite::unbox('asc')),
list(jsonlite::unbox(2), jsonlite::unbox('desc'))
))) On the other hand, when |
The only thing that makes me a little nervous is that we introduce undefined behavior for |
Can you give an example? In my mind it seems pretty clear: For things like |
Also, if you'd prefer an option for this behavior, I'm amenable to that as well -- although to me it doesn't seem necessary since |
Oh, I just realized that you have a class named |
Sorry I was confused. I meant the case of |
Exactly. It is harmless. |
Big thanks for this, but it should be documented. Maybe in |
For compatibility with RJSONIO, objects wrapped in
I()
shouldn't be unboxed, even whenauto_unbox=TRUE
.For example:
@jeroenooms would this just involve writing a new method for
AsIs
objects?This is related to timelyportfolio/parcoords#6.
The text was updated successfully, but these errors were encountered: