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
parse_chidmessageid includes old code paths for parsing legacy notification chidmessageid formats. This along with similar code in autoush-common’s Notification::chidmessageid and RangeKey::legacy_version should be removed as we no longer support these types of notifications.
Alongside the removal from Notification I think this struct could further enforce topic vs timestamp messages (without the need to support legacy types) by converting the topic and sortkey_timestamp fields into an enum:
parse_chidmessageid
includes old code paths for parsing legacy notificationchidmessageid
formats. This along with similar code in autoush-common’sNotification::chidmessageid
andRangeKey::legacy_version
should be removed as we no longer support these types of notifications.Alongside the removal from
Notification
I think this struct could further enforce topic vs timestamp messages (without the need to support legacy types) by converting thetopic
andsortkey_timestamp
fields into an enum:┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: