Skip to content

feat(sps): use internal_date_ts for updated_at_seconds on email#622

Merged
whutchinson98 merged 1 commit intomainfrom
hutch/bac-170-correctly-use-the-email-db-internal_date_ts-field-when
Dec 15, 2025
Merged

feat(sps): use internal_date_ts for updated_at_seconds on email#622
whutchinson98 merged 1 commit intomainfrom
hutch/bac-170-correctly-use-the-email-db-internal_date_ts-field-when

Conversation

@whutchinson98
Copy link
Copy Markdown
Member

Summary

Screenshots, GIFs, and Videos

@whutchinson98 whutchinson98 requested a review from a team as a code owner December 15, 2025 16:48
@linear
Copy link
Copy Markdown

linear bot commented Dec 15, 2025

Comment on lines +28 to +32
let updated_at = message_info
.internal_date_ts
.map(|date| EpochSeconds::new(date.timestamp()))
.transpose()?
.unwrap_or(now);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code is repeated, could we dry it up? Also should we be erroring if the time doesn't exist? idk if it makes sense to insert now

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think having it be now since it is optional and we still want to store the email is valid

@whutchinson98 whutchinson98 merged commit c2ffb86 into main Dec 15, 2025
36 checks passed
@whutchinson98 whutchinson98 deleted the hutch/bac-170-correctly-use-the-email-db-internal_date_ts-field-when branch December 15, 2025 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants