wacrm/src/components/inbox
Arnas Donauskas 208b096cb1
chore(flows): defensive gate on interactive bubble render
Wraps the new `case 'interactive'` rendering with `isFlowsEnabled(profile)`
from the beta-features module that landed in #113. Non-beta accounts
fall back to the plain-text rendering for `content_type='interactive'`
rows — they get the option title as text, no special "↩ Button reply"
affordance.

Why this gate exists even though the case is unreachable today:
  - No code path on this branch produces `content_type='interactive'`
    rows. The flow runner that does is upcoming (PR #2), and it'll be
    behind the same gate.
  - But: if a stray interactive row ever shows up in a non-beta
    account (manual SQL insert, data import, future bug), we'd rather
    the account see boring plain text than UI for a feature they
    haven't opted into.
  - The cost is ~3 LoC and one hook call. Pure paranoia insurance.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-22 13:21:22 +03:00
..
contact-sidebar.tsx chore: switch accent palette to Hostinger violet, drop emerald green 2026-05-06 11:57:12 +03:00
conversation-list.tsx fix(inbox): replace broken updater-closure flag, add reconnect/visibility resync 2026-05-21 19:30:48 +03:00
message-actions.tsx fix(inbox): scope hover to the bubble; fix stale-closure reaction flow 2026-05-19 16:32:34 +03:00
message-bubble.tsx chore(flows): defensive gate on interactive bubble render 2026-05-22 13:21:22 +03:00
message-composer.tsx feat(inbox): reactions, reply-to, and copy on chat messages 2026-05-19 16:17:26 +03:00
message-reactions.tsx feat(inbox): reactions, reply-to, and copy on chat messages 2026-05-19 16:17:26 +03:00
message-thread.tsx Merge pull request #111 from ArnasDon/feat/inbox-doodle-background 2026-05-22 10:09:16 +03:00
reply-quote.tsx feat(inbox): reactions, reply-to, and copy on chat messages 2026-05-19 16:17:26 +03:00
template-picker.tsx feat(inbox): wire up the template picker dialog 2026-05-18 15:25:45 +03:00