Currently, the backend determines whether a flowsheet entry is a talkset or breakpoint by parsing the message string (checking if it contains "Talkset" or "Breakpoint"). This is fragile and prevents the backend from distinguishing entry types reliably when messages are customized.
Add an optional entry_type field to the message variant of FlowsheetSubmissionParams and pass it from all talkset and breakpoint buttons in both the modern and classic experiences. This lets the backend determine the entry type from a structured field rather than parsing the message string.
Changes
lib/features/flowsheet/types.ts: Add optional entry_type?: 'talkset' | 'breakpoint' | 'message' to the message variant of FlowsheetSubmissionParams- Modern experience: Update
TalksetButton.tsx and BreakpointButton.tsx to pass entry_type
- Classic experience: Update
Main.tsx handlers for handleAddTalkset and handleAddBreakpoint to pass entry_type
Corresponds to backend change: WXYC/Backend-Service#239
Currently, the backend determines whether a flowsheet entry is a talkset or breakpoint by parsing the message string (checking if it contains "Talkset" or "Breakpoint"). This is fragile and prevents the backend from distinguishing entry types reliably when messages are customized.
Add an optional
entry_typefield to the message variant ofFlowsheetSubmissionParamsand pass it from all talkset and breakpoint buttons in both the modern and classic experiences. This lets the backend determine the entry type from a structured field rather than parsing the message string.Changes
lib/features/flowsheet/types.ts: Add optionalentry_type?: 'talkset' | 'breakpoint' | 'message'to the message variant ofFlowsheetSubmissionParamsTalksetButton.tsxandBreakpointButton.tsxto passentry_typeMain.tsxhandlers forhandleAddTalksetandhandleAddBreakpointto passentry_typeCorresponds to backend change: WXYC/Backend-Service#239