MarekWo e14c4fab06 fix(channels): include message id in /api/messages response ...

/api/messages was dropping channel_messages.id when building the response
dict. The frontend therefore had msg.id=undefined for history-loaded rows,
so createMessageElement's "typeof msg.id === 'number'" guard suppressed
the raw-resend button, and refreshMessagesMeta couldn't find the wrappers
either (data-msg-id only gets set when msg.id is truthy). End result: the
raw-resend button only appeared on messages sent in the current session
and was lost on every channel switch or page reload.

Surfacing id costs nothing — the field already exists on the row — and
also unblocks any future per-message UI that needs to address the row
directly. createMessageElement already handles undefined id correctly for
older clients, so this is a one-way frontend benefit.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-06-09 19:06:08 +02:00

..

__init__.py

Phase 1: Backend basics - Complete Flask application with REST API

2025-12-21 14:02:46 +01:00

api.py

fix(channels): include message id in /api/messages response

2026-06-09 19:06:08 +02:00

views.py

fix(connection): self-heal degraded long-lived TCP via in-place reconnect

2026-06-07 21:10:03 +02:00