Using this issue to collect API deserialization errors due to missing fields.
-
The field url in the Activity struct is not always sent by the API, causing a parse error on occasion.
This can be seen for example when receiving a Meeting event on meeting closure.
-
The field global_id can be missing to build a Target struct. This was seen when receiving a delete (?) activity
These are minor as long as the crate does not support the associated event types, but it would be cleaner to make the fields optional.
Using this issue to collect API deserialization errors due to missing fields.
The field url in the
Activitystruct is not always sent by the API, causing a parse error on occasion.This can be seen for example when receiving a Meeting event on meeting closure.
The field global_id can be missing to build a
Targetstruct. This was seen when receiving a delete (?) activityThese are minor as long as the crate does not support the associated event types, but it would be cleaner to make the fields optional.