use_r() and use_test() come from usethis. Both usethis and devtools are loaded by my .Rprofile, I recommend taking some time going through the usethis setup article.
Any feedback on that guide, this issue, the endpoints issues is welcome. My instructions are not perfect at all and it'd be good to improve them.
There's a sort of exemplary PR #83. Looking through scripts of other functions (not the deprecated ones) is also useful.
To define what useful tidiers could be, discuss with @stephlocke + think of what you'd like to work with in a report using Hubspot data.
There's no priority order for the open issues. I'd suggest to start with one you're familiar with as a Hubspot user, and if none is known to you, then with one that has only a few parameters.
Ignore the "o_auth_access_token_or_api_key" argument since there are a token and an apikey argument.
Also ignore the "offset" parameter, that we deal with internally.
The automatic names of functions are not necessarily very good. The pattern hs_<endpointname in snake case>_raw() is compulsory but e.g. prepositions should be dropped from the endpoint name.
I think there can only be one details section per Rd so when documenting view do that below the existing @details section of the R script template.
For endpoints that have arguments related to properties and property history (e.g. tickets), refer to what's been done in contacts.R in particular.
use_r()anduse_test()come fromusethis. Bothusethisanddevtoolsare loaded by my .Rprofile, I recommend taking some time going through the usethis setup article.hs_<endpointname in snake case>_raw()is compulsory but e.g. prepositions should be dropped from the endpoint name.viewdo that below the existing@detailssection of the R script template.