jennybc
commented
5 years ago A few things come to mind:
- googledrive has new features to help you express "create this thing, if it doesn't exist yet, and update it if it does". See this section of the v1.0.0 release notes. The file in question could be a Google Sheet.
- The metadata you get from
googledrive::drive_get()includesmodifiedTime, which you could work with to determine if something has changed. - There is formal tooling around revision history for Drive files (which includes Sheets): https://developers.google.com/drive/api/v3/manage-revisions. So far googledrive doesn't offer any high-level functions around that. But if there was demand, we could. The low-level API in googledrive would already make such calls reasonably pleasant.
Also ...
Just so you know, googlesheets (this package) is being sunsetted very soon, in favour of a successor googlesheets4:
https://github.com/tidyverse/googlesheets4
Also, depending on what you're doing, a great deal of googlesheets's functionality (this package) can be accomplished with the already-released and actively-maintained googledrive package:
https://googledrive.tidyverse.org
Anything that operates at the whole file level can be done with googledrive and, even here, has always involved calls to the Drive API instead of Sheets.
So, in terms of developing your workflow, I recommend you look towards those packages as dependencies and not googlesheets.
The Sheets v3 API and therefore the original googlesheets package will go offline in March 2020:
joepowers16
The googlesheets R package has been invaluable for my team's workflow, but I am unsure of how to automate the execution of R scripts after a prerequisite Google Sheet is updated. If the Google Sheet were a static csv file, then the use of a Makefile would be straightforward. Do you have advice about how (or plans to add a feature that would) integrate Google Sheets into a Makefile based workflow?