You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realize chrono is currently neatly integrated with firestore-rs but would there be a downside to also supporting google.protobuf.Timestamp and std::time::SystemTime when it comes to serializing and deserializing timestamps?
Would be happy to pull a PR together if you were open to this and had a preferences on how it would be implemented.
Also as an aside we have tried to stick with time instead of chrono so ideally chrono would be a default feature we could disable.
The text was updated successfully, but these errors were encountered:
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 had.
Nowadays, there is a plenty good choices:
time
jiff
Now the problem is that somehow give a choice for date/time integration (not so disruptive for the current users).
Probably it needs to introduce some internal type based on something like std::time or Timestamp and optional (feature gated) conversion for different crates out there.
Of course I'm open to any contributions here, since I'm focusing a bit on different stuff for now and it would be great if someone can implement this.
I realize chrono is currently neatly integrated with
firestore-rs
but would there be a downside to also supporting google.protobuf.Timestamp and std::time::SystemTime when it comes to serializing and deserializing timestamps?Would be happy to pull a PR together if you were open to this and had a preferences on how it would be implemented.
Also as an aside we have tried to stick with time instead of chrono so ideally chrono would be a default feature we could disable.
The text was updated successfully, but these errors were encountered: