Closed dwinter closed 9 years ago
This is fixed but by a workaround. It happens because I use rbind
to build the data frame and it converts everything into a string.
This part of the code uses too much "black magic" as you noticed... and I think that using purrr to build the data frame would probably make things easier. I'll try to look into it....
Nice one @fmichonneau,
When I've run into similar problems, being able to specify rbind.data.frame
when collecting up the rows has helped (since they are data frame rows that won't be coerced to one class). Don't know if it would help in this case, just a heads up for something to check out.
unfortunately, it doesn't work in this case :sob:
The
data.frame
returned bytnrs_match_names
contains columns that, as far as I can tell, always contain logical/boolean values. However, they end up being represented as characters in the returned object:It would be nice to be able to use these values to subset the
data.frame
but that doesn't work at the moment (though of course you could coerce them to locicals):I would have a god at his myself, but don't quite understand the black magic you are weaving to create these dataframes in the first place @fmichonneau!
Can this be done easily? Since they already look like R
logical
s I wonder if they are being coerced to characters somewhere along the way?