A modern programming language that makes developers happier.

kotlinlang

docs.png

gdrive.png

Google, why do you do this to me? :face_with_rolling_eyes::sweat_smile::melting_face:

This is a good example of why debugging is useful: when you're using some unfamiliar API and you're like "WTH is going on". A bunch of printlns might be able to save you, but exploring around in a debugger will yield faster results usually

the docs could use an example, I am not sure how to interpret `This method accepts the q parameter` with `use the trashed=false query parameter`, I suspect they mean `q=trashed=false` but an example would help. documentation is hard (and debug useful)

Bildschirmfoto 2025-01-09 um 15.44.47.png

Oh, yes... `q=trashed=false` works.

<https://developers.google.com/drive/api/reference/rest/v3/files/list> is so confusing, because they call `trashed` a "query parameter", but it's not in the list of query parameters. But for the usage of `q` there is actually a sample including `trashed`.

Google Drive Docs are a mess :smile:

image.png

oh, the feedback functionality is a nice touch, curious how long it will take to get a feedback (or if they will just update the docs)

I'll let you know. :slightly_smiling_face:

I'm sorry, WHAT? `q=trashed=false`??? Maybe I'm just bad at reading docs, but I wouldn't have guessed that in my wildest dreams. I'm sure there's a "perfectly reasonable" explanation for how that came about, but it's still unintuitive

Bildschirmfoto 2025-01-09 um 16.57.55.png

Yeah, on the next page is the thing that gave a hint to that.
I wouldn't have guessed that, too. :smile:

The whole Google Drive API is questionable.

I guess it's somewhat consistent with Google Search, where the search term is a value of the `q` query parameter. In the Google Drive API it looks like everything that specifies restrictions on which files to list is a value of the `q` parameter.