Skip to content

Fix message entries stored as 'track' instead of 'message' entry type#239

Merged
jakebromberg merged 2 commits intomainfrom
bugfix/talkset-entry-type
Mar 19, 2026
Merged

Fix message entries stored as 'track' instead of 'message' entry type#239
jakebromberg merged 2 commits intomainfrom
bugfix/talkset-entry-type

Conversation

@jakebromberg
Copy link
Copy Markdown
Member

Summary

  • Set entry_type: 'message' explicitly when creating flowsheet entries from the message code path (talksets, breakpoints, PSAs, etc.)
  • Add parameterized unit tests covering message entry creation and verifying track entries are unaffected

Closes #238

@jakebromberg jakebromberg force-pushed the bugfix/talkset-entry-type branch from 8310d29 to 2b898d2 Compare March 18, 2026 21:37
Infer entry_type from message content (talkset/breakpoint/message) matching the FlowsheetEntryType discriminated union in wxyc-shared. Accept explicit entry_type in POST body when provided, falling back to inference for backwards compatibility.

Closes #238
@jakebromberg jakebromberg force-pushed the bugfix/talkset-entry-type branch from 3d78034 to e0f9782 Compare March 19, 2026 03:29
Messages are now correctly stored as entry_type 'message' instead of
'track', so the V2 transform returns them without metadata fields
rather than with null metadata fields.
@jakebromberg jakebromberg merged commit 45c962a into main Mar 19, 2026
4 checks 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.

Talkset and breakpoint entries stored as 'track' instead of correct entry type

2 participants