Migrate to gargle

[MarkEdmondson1234]

I suggest this package migrates to use gargle rather than googleAuthR which largely is just wrapping gargle at the moment anyway. googleAuthR is under threat of being removed from CRAN every few years when CRAN has a new policy on full stops or similar, so its an unreliable dependency.

[maelle]

@cherylisabella have you seen this issue?

Thank you @MarkEdmondson1234

[cherylisabella]

Hi @maelle, of course!

I successfully pushed the latest version of googleAuthR to CRAN last month, so downstream packages depending on it (including googleLanguageR) can continue to function without disruption.

I’ve also discussed taking over maintenance of googleAuthR with the current maintainers, and they’ve agreed in principle via email. However, the formal transfer of the repository and maintainer role has yet to take place.

Let me know how you’d like to proceed from here.

[maelle]

I am not a Google API expert at all, but from what @MarkEdmondson1234 it seems the best way forward might still be to use gargle to which GoogleAuthR is a wrapper? Or am I mistaken? Thank you in any case 😸