chainsawriot

@TimBMK If you don't mind, I can deal with the undeclared dependency. The usage of `.` in the previous case is different from the current instances. In the previous case,...

@TimBMK That's a nice suggestion. But please keep it at "one feature, one PR". Or else, it would be extremely difficult to dissect the git history later.

@johnhenrypezzuto It is not available. Would you like to read through the Twitter V2 API documentation, see if it is possible? If it is possible: try to implement this feature,...

#349 is also a manifestation of this because a "column" in a tibble is not a vector.

Another way to deal with it is to save the `r` here instead. It would be what users using [twarc2](https://twarc-project.readthedocs.io/en/latest/twarc2_en_us/) would expect. It would save a lot of time for...

@cjbarrie @justinchuntingho Any thought? #304, #305, and #307 can't be solved without handling this one first.

@cjbarrie Simply save this guy: r If you need it to be json ```r response

@TimBMK Yes, Twitter changes the data returned by the API all the time and we are always in the passive position. The core data structure wouldn't change a lot though....

# Stage 1 master branch - [ ] Modularize the current functionalities to handle the json-based format in - [ ] `bind_tweets` - [ ] `resume_collection` - [ ] `update_collection`...

@TimBMK It is not always empty. For example, in the case above the `errors_.json ` is not empty. ``` r require(academictwitteR) #> Loading required package: academictwitteR FFF value detail title...