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

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 9de273d4-e565-4398-9ef2-4c80dafac086

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}