refactor: serialize slice fact event bodies semantically #60
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Slipstream/emc!60
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refactor/slice-fact-typed-event-body"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Rationale
Verification
The refactor introduces a new serialization format for slice fact events while maintaining backward compatibility with legacy formats. The changes appear well-structured and safe to merge, with comprehensive tests ensuring both new and legacy formats are handled correctly.
Walkthrough
SliceFactEventserialization to use a newbodyfield instead ofexported_event_typeandpayload.SerializedSliceFactEventto handle both new and legacy formats during deserialization.ExportedEventBodyfor converting to and from the new tagged JSON format.LLM usage and cost
Estimated total USD: $0.021175 via https://api.openai.com and https://api.openai.com