Backend: Remove str-based EventUpdate items#9320
Conversation
Removes the deprecated updated_str_items field from both the EventUpdate notification data message and the GenerateEventUpdateNotificationsPayload internal job payload, reserving the field numbers and names so they can never be reused. The i18n-friendly updated_enum_items field is now the sole source. Also drops the now-unused _updated_item_str_to_enum helper. Fixes #9117 Co-authored-by: Tristan Labelle <2314287+tristanlabelle@users.noreply.github.com>
MobileInstall the Dev Tool (iOS via TestFlight, iOS Simulator, or Android .apk) here. Scan the QR with your phone camera, or tap Open in Dev Tool on the device, to open this branch in the installed Dev Tool dev client.
Deep linksiOS Android Web (Vercel)View the Vercel web preview for this branch. Backend
Other
|
📝 Release NotesThis PR does not need to be included in release notes. Reason: This PR removes deprecated backend/internal notification fields and cleanup code after a migration. It does not add or change any noticeable user-facing behavior, and the technical work is routine maintenance rather than a major infrastructure or reliability improvement worth highlighting to end users. 🤖 Bot Debug InformationModel: |


Removes the deprecated
updated_str_itemsfield from both theEventUpdatenotification data message and theGenerateEventUpdateNotificationsPayloadinternal job payload, reserving the field numbers and names. The i18n-friendlyupdated_enum_itemsfield is now the sole source.(a month has passed since I migrated us over so it should be safe that there are no old queued jobs using
updated_str_itemsanymore.)Fixes #9117
Generated with Claude Code