|
|
|
|
|
by dmitriid
1812 days ago
|
|
> I'm pretty sure if you have the time to make a PR to fix it, it would be welcome. Google had a net income of $17.9 billion in just Q1 of 2021. I believe they have the resources to fix that, and I will not be shamed into "if you have time, please open a PR towards this opensource project". > But I'm guessing it's non trivial or it would have been fixed by now - probably a quirk of the code generation logic. I remember the "quirks of generation logic" being used as an excuse for Google's horrendous Java APIs towards their cloud services. "It's just how we generate it from specs and don't have the time to make it pretty". For the life of me can't find that GitHub issue that called this out. Somehow their other APIs (for example, .net) are much better. Edit: found it https://github.com/googleapis/google-cloud-java/issues/2331#... and https://github.com/googleapis/google-cloud-java/issues/2331#... |
|
I recall a little more than half a decade ago settling on the PHP version of their Geocoding API client library for a project because it was the only one whose documentation matched how you were actually supposed to authenticate.