Abdulla Abdurakhmanov

@domoritz It is good if it works for you. Though I'm still curious if you able to read this stream anyhow? Looking at many APIs (like for Python, etc), they...

> So yes, I do need a schema in the byte stream Ok, then in this case this change won't work for you since schema is basically absent in the...

Hey, yes, this is my long term concern as well. The time I started working with Firestore (it wasn't even published here yet), chrono was almost single choice that we...

And I don't think there is no need to make `chrono` somehow special one (or even default one).

It is not something that supported internally. Perhaps you want to have a look solutions like https://crates.io/crates/backoff for this.

This is mostly coming from confusion between Firestore and Firebase. This crate works specifically on backend with Firestore (and gRPC protocol) which uses GCP service accounts, not API keys. Firebase...

The most secure and recommend way is actually to leverage Google Workload Identity without any keys if your application deployed on GCP. Keys are usually needed if it is deployed...

I'm closing this for now, let me know if you have additional questions for this.

Hey, REST APIs are generated and patched manually by external contributors since Google doesn't provide them officially. So they might missing information or incorrect (we had to patch some fields...

Since it is not available through gRPC, this can be supported natively if we can copy this: https://github.com/APIs-guru/openapi-directory/tree/main/APIs/googleapis.com/fcm/v1 (REST specs are updated/refreshed manually, gRPC updated automatically once in month) I...