I've noticed a lot of inconsistency in example code given in various API documentation (I have looked at Calendar API, Directory API, Sheets API, YouTube API, and Drive API. I'm API-ed out). All of it uses this library, but some are using client_secret.json and others are using client_secrets.json. This repo seems to use client_secrets.json consistently so I don't understand why client_secret.json (no s) is being introduced.

But it is being introduced: see e.g. this commit to the youtube api samples that changes client_secrets.json to client_secret.json. (Is this an official source of samples? a google person developing a side project? supported unofficially but officially? the chain of ownership here is left ambiguous and that's frustrating. their contributing document points to this repo.)

Meanwhile the calendar sample is hosted in this repo and uses client_secrets.json consistent with the rest of the repo.

In spite of all this, sometimes even the incorrectly-named file seems to work. What's going on here?