communication: list_messages + stamp timestamps #27
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_osis!27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_add_list_messages_and_timestamp_trigger"
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
Two communication-domain changes:
Add
ConversationService.list_messages(conversation_sid) -> [ChatMessage]— #26Server-side filter sorted by
created_atascending. Removes the client-side N+1 where opening one chat meant listing every message SID in the entire domain and fetching each one individually. In the messaging UI this drops chat-open from ~51 RPCs to 3.Stamp
created_at/updated_atinchatmessage_trigger_save_pre— #25Previously a no-op, so every saved message had
created_at = 0and rendered as00:00/Jan 1 1970downstream. The trigger is the right place because it catches every save path (send, reply, react, future handlers).Generated code
*_generated.rs,openrpc.json, and the SDK client method are the output of the schema build; committed so downstream consumers (e.g.hero_archipelagos) can pick up the new method without re-running the generator.Test plan
cargo check -p hero_osis_servercargo clippy -p hero_osis_server— no new warningsconversationservice.list_messagesdiscoverable viarpc.discoverChatMessage.created_atis non-zeroUnblocks the companion PR in
hero_archipelagosthat switchesfetch_messagesto this new endpoint.communication: add list_messages + stamp message timestampsto communication: list_messages + stamp timestamps