chainsawriot
chainsawriot
[FR] Add "reply_count" column in the "bind_tweets(data_path = "tweetdata", output_format = "tidy") "
@Qiegao1994 Thanks for raising this. And the `tidy` format is opinionated and thus it doesn't include the `reply_count` by default. You may see the relevant code here. https://github.com/cjbarrie/academictwitteR/blob/5ed91fff98294f2d554d74aa1a911dc23d62c684/R/bind_tweets.R#L101-L104 If you...
@TimBMK Thanks for reporting the bug. I can reproduce this. ``` r require(academictwitteR) #> Loading required package: academictwitteR users [1] "data_.json" "data_848204306566320128.json" #> [3] "data_848950153520218113.json" "query" #> [5] "users_.json" "users_848204306566320128.json"...
@TimBMK I will keep this issue focusing on only the second issue. And I will open another issue related to the first one.
@cjbarrie I would like to make a correction that `page_n` will be in the `params` anyway by [get_tweet](https://github.com/cjbarrie/academictwitteR/blob/7a1a2dc758332039e7bfbadc399865a24c647478/R/utils.R#L36). If we are going to store `params`, `page_n` is automatically recorded.
It could be something like this ``` r require(academictwitteR) #> Loading required package: academictwitteR params
Short answer: the data are there. But the mechanism to extract those geo data is yet to be developed. In the meantime, you can either use the `place_id` to join...
@sadettindemirel It is available only from the API 1.1, not 2.0 (yet). https://developer.twitter.com/en/docs/twitter-api/v1/trends/trends-for-location/api-reference/get-trends-place academictwitteR's aunt [rtweet](https://github.com/ropensci/rtweet) has `get_trends`, go check that out.
@msaeltzer You know this right? ``` r require(academictwitteR) #> Loading required package: academictwitteR res [1] NA NA NA #> [4] NA NA NA #> [7] NA NA NA #> [10]...
@cjbarrie The reason why `setdiff` is used in my suggestion is that the `errors` option (proposed in #264) will reorder the `id` column. Although most of the time it is...
@TimBMK TODO - [x] Please run `devtools::document()`; commit also `bind_errors.Rd` Do you know how to write tests? If yes, it would be useful.