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
While our transformations currently have a pretty decent API, there is one big drawback to the current class-based piping/chaining approach: the transformations are not tree-shakeable. This means that you always send the code of all transformations to the client.
I think I just came up with an approach to circumvent this problem. Say that we want to do this with the current API:
While our transformations currently have a pretty decent API, there is one big drawback to the current class-based piping/chaining approach: the transformations are not tree-shakeable. This means that you always send the code of all transformations to the client.
I think I just came up with an approach to circumvent this problem. Say that we want to do this with the current API:
In the new proposed API, this would become
The advantages of this method are
DataContainer
(if you are using column-oriented data at least)An example of how a user could write a custom
toQuantitative
transformation to convertcategorical
data toquantitative
data:Thoughts?
The text was updated successfully, but these errors were encountered: