Skip to content

Make ts optional in SlackEventSkeleton#429

Merged
jaredstehler merged 1 commit intoHubSpot:masterfrom
dbinit:dbinit/fix-event-skeleton-ts
Feb 17, 2026
Merged

Make ts optional in SlackEventSkeleton#429
jaredstehler merged 1 commit intoHubSpot:masterfrom
dbinit:dbinit/fix-event-skeleton-ts

Conversation

@dbinit
Copy link

@dbinit dbinit commented Feb 17, 2026

Summary

  • SlackEventSkeleton is the catch-all model for ~30 event types without dedicated model classes. Many of these (e.g. reaction_added, reaction_removed, pin_added) don't include a ts field — only event_ts. This causes InvalidImmutableStateException at deserialization time.
  • Added a default getTs() override returning null, following the same pattern used by SlackAppHomeOpenedEventIF and other event interfaces in this codebase.

🤖 Generated with Claude Code

…ts without ts

Many Slack event types (reaction_added, reaction_removed, pin_added, etc.)
only include event_ts, not ts. Since SlackEventSkeleton is the catch-all
model for ~30 unmapped event types, it should tolerate missing ts rather
than throwing InvalidImmutableStateException.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@dbinit dbinit marked this pull request as ready for review February 17, 2026 20:46
@jaredstehler jaredstehler merged commit 2066ad3 into HubSpot:master Feb 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants