Why the management overhead of a new googlesheets for each of Google API versions?

Is the reason given in googlesheets4's README the only one?

It seems to me that this would mean locking yourself into a cycle of starting a new package, setting up its infrastructure, migrating older issues to the new repo, etc.. when Google updates their API in the future.

Was that seen as less work than keeping googlesheets stable & updated internally to the next API version, plus maybe adding version-specific parameters where needed or useful?

Since Jenny Bryan has developed both, I'm gonna go ahead and say yes to this. The implementation is sufficiently different, that it made more sense to use a separate package.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.