feat: add status message sending#247
Conversation
f5ecfe1 to
0294721
Compare
dinakars777
left a comment
There was a problem hiding this comment.
Nice work — code quality looks solid. Single clean commit, proper regression tests for both text and media statuses, idempotent schema migration, and clean separation from the regular messages table. CI is all green.
A couple of observations before we merge:
-
Migration placement: The new columns are added via
migrateStatusMessageMediaColumnsinsidemigrateCoreSchemarather than as a numbered migration in the existingmigrations.gosequence. Worth checking if Peter prefers the numbered approach for new tables. -
Scope check: This is a sizeable feature (+609 lines, new DB table, new CLI command). @steipete — does status message support fit the current roadmap? Happy to merge once you give the thumbs up.
|
Hi @dinakars777, totally agree. Let's wait for confirmation. The reason I added it is that I saw status updates in my messages list yesterday and had to check who that contact was because I hadn't had a conversation with that person in a long time. |
0294721 to
c16ce25
Compare
Summary
wacli send statusfor WhatsApp status broadcasts viastatus@broadcast.--file, optional--mime, and--messageas the media caption.status_messagestable, including sender fields, media metadata, and text-status styling fields.messageslist/search/export behavior.Test Plan
go test ./cmd/wacli ./internal/store ./internal/appnode scripts/build-docs-site.mjsgit diff --check upstream/main..HEADNotes
pnpm testwas run earlier and still fails oninternal/fsutil TestEnsureWritableDirRejectsNonWritableDirwhen executed as root, because root can write to the chmod-restricted test directory. The status-related cmd/store/app tests pass.