Skip to content

Conversation

@jeremystretch
Copy link
Member

Closes: #21303

  • Extend to_objectchange() to cache the serialized data as _postchange_snapshot on the instance being serialized.
  • Modify get_snapshots() to check for cached serialized data before running serialization.

@jeremystretch jeremystretch requested review from a team and pheus and removed request for a team January 29, 2026 21:44
Copy link
Contributor

@pheus pheus left a comment

Choose a reason for hiding this comment

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

Thanks! Just two small nits below.

I’m not strongly opinionated about either of them, so I’m leaving this as a comment-only review and I’m happy with the PR as-is.

@jeremystretch jeremystretch requested a review from pheus January 30, 2026 19:12
Copy link
Contributor

@pheus pheus left a comment

Choose a reason for hiding this comment

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

Awesome! Thanks, @jeremystretch !

@jeremystretch jeremystretch merged commit aa4a9da into main Jan 30, 2026
12 of 13 checks passed
@jeremystretch jeremystretch deleted the 21303-cache-post-change-data branch January 30, 2026 19:49
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.

Cache post-change data on the instance after serialization

3 participants