Closed sharlagelfand closed 3 years ago
@sharlagelfand yes, for facet faking I use "x" and "y" hardcoded. Like the idea of datamations_x
and datamations_y
.
Agree on datamations_x
and datamations_y
. To facilitate merging correctly, @giorgi-ghviniashvili can make the update to the JS side first, then @sharlagelfand will pull in the changes to htmlwidget
and reflect them on the R side.
Hi, I created config.js
and specified this field name there. See this commit.
You can change datamation_x
to anything else, e.g. dub_dub_x
, dub_dub_y
.
Thanks @giorgi-ghviniashvili! I integrated that code into mine and also added a config file on the R side so it's not hard coded throughout - good idea! Seems to be working well, haven't found any cases where it breaks 🤞🏻. I'll create a pull request with the changes!
Currently the code errors if there's already a column in the data named
y
(and will definitely be an issue if the variable being summarised or grouped is namedy
) because we're using that internally - need to dig in and rename to a more "system" type of name, same forx
. I don't think we can use something like.x
and.y.
(which would be more like "systems names" in R) because they won't work with JS, so probably just something likedatamations_x
anddatamations_y
@giorgi-ghviniashvili does the JS code use the actual "x" and "y" (and "y_raw") variables, or just looks for what is in the "x" and "y" encoding in the specs? Just trying to figure out if we need to coordinate changing this