feat!: move to timestamps in response models

[szuperaz]

Relevant stream-chat-js PR: GetStream/stream-chat-js#1849

Breaking changes

• MessageListProps.headerPosition is now nanoseconds
• ChatContextValue. latestMessageDatesByChannels record now stores nanoseconds instead of Dates
• VirtualizedMessageListProps. lastReadDate is now nanoseconds instead of Date
• ProcessMessagesContext.lastRead is now nanoseconds instead of Date
• ProcessMessagesParams.lastRead is now nanoseconds instead of Date

The change can produce runtime errors not caught by TS compiler; integrators should check their code for these potential issues:

# the idioms that now fail silently
grep -rn "isDate(\|instanceof Date\|\.getTime?\?\.\?(\|as string | Date" src

# raw timestamps interpolated into translations
grep -rn "t(.*timestamp\|t(.*date" src

# every surviving `new Date(x)` with an argument
grep -rn "new Date([^)]" src

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}