Skip to main content

React v7 UI Kit — Dashboard-Enablement & Stitching Audit

Scope: ui-kit/react (v7 only — the default version). Audits every feature/component whose doc describes something that (a) must be enabled in the CometChat Dashboard, or (b) requires manual “stitching” (developer wiring: event handlers, connecting components, required props, navigation callbacks, SDK setup). For each, it records whether the page already links to a feature guide / “how it works” reference, and what link/reference should be added and where. Legend — Type
  • Dashboard — a Dashboard extension / AI feature / add-on / setting must be turned on for this to work.
  • Stitch — developer code required (handlers, required entity props, connecting components, SDK calls).
  • Both — needs Dashboard enablement and wiring.
Reference status
  • Yes = links to the right guide · Partial = inline example or component card only, no guide link · No = points to nothing.

Part 1 — Dashboard-enablement required

These render/behave only when a Dashboard extension, AI feature, add-on, or app setting is enabled. Most auto-integrate in code, so the docs should say “enable X in the Dashboard” and link the feature guide.

Part 2 — Stitching (developer wiring) required

These do nothing (or nothing useful) until the developer writes connecting code. The docs mostly show inline examples but rarely link to the how-to guide that walks the pattern end-to-end.

Part 3 — Systemic / high-priority patterns

A. plugins/overview says “no configuration needed” — misleading for extension-backed content

All four extension bubbles (Poll, Sticker, Collaborative Document, Collaborative Whiteboard) route their “how it works” reference through plugins/overview#built-in-plugins, which states plugins are “included automatically — no configuration needed.” That’s true for the UI Kit renderer but false for the Dashboard extension that produces the message. Fix once at the source (add a “Requires the X extension enabled in the Dashboard” note + link on the extension_* rows), then add the same note on each bubble page (#5–#8, #26).

B. Calling pages have no upfront prerequisites

call-buttons, incoming-call, outgoing-call, call-logs never mention the Calls SDK install or .setCallingEnabled(true) on their own page, and don’t link to calling-integration/call-features. A reader can copy the minimal render and see nothing render. Also: call-features.mdx (the overview) omits a link to calling-integration.mdx (the actual step-by-step setup), and calling-integration.mdx doesn’t link out to the standalone call-buttons/incoming-call/outgoing-call component pages. (#17, #18, #54–#57)

C. AI (“Smart Chat”) features are never linked from component pages

ai-features.mdx exists but is not linked from message-header (Summary), message-list (Smart Replies, Conversation Starters), or message-composer (AI button). ai-assistant-chat has no link to any AI-Agent Dashboard-setup guide despite requiring a Dashboard-configured agent user. (#11–#15, #19, #27) event-system.mdx lists events that power the guides but links to none of them; the guides use the events but don’t link back:
  • ui:user/blocked / ui:user/unblockedguide-block-unblock-user
  • ui:open-chatguide-message-privately
  • ui:thread/opened / ui:thread/closedguide-threaded-messages
  • ui:group/createdguide-group-chat-setup
Also, no component page (“Events Received/Emitted” tables) links to event-system.mdx at all. (#32, #35, #38, #42, #46, #49, #68–#70)

E. Content-integrity contradiction (flag for docs owner)

Plugin registration order conflicts across pages:
  • plugins/text-formatters.mdx (line ~142): custom plugins are “prepended before the defaults… your custom text plugin takes precedence.”
  • plugins/overview.mdx (~line 76) and plugins/custom-plugin.mdx (~line 124): custom plugins are “appended after the defaults, so default plugins keep priority.”
These directly disagree on ordering. Not a dashboard/stitch gap, but it will confuse anyone wiring a custom formatter — reconcile before adding more cross-links.

Summary

  • Files audited: ~50 (all React v7 UI Kit .mdx).
  • Total findings: ~70 (28 dashboard-enablement, ~42 stitching; overlaps counted once by primary type).
  • Dashboard-enable (pure): message-list Translate & Flag/Moderation, composer Polls/Collab/Stickers & file limits, sticker bubble, video thumbnails, core-features read-receipts, plugins/overview extension plugins.
  • Both (dashboard + stitch): all calling components & header call buttons, all AI features (Summary, Smart Replies, Starters, AI button, AI Assistant Chat, agent chat), poll/collab-doc/collab-whiteboard bubbles, flag dialog, campaigns/notification-feed, presence, provider init.
  • Missing a reference entirely (No) or only Partial: the large majority — the six how-to guides, extensions.mdx, ai-features.mdx, calling-integration.mdx/call-features.mdx, and event-system.mdx all exist but are rarely linked from the component pages they explain.
Top 6 fixes (highest impact):
  1. plugins/overview — correct the “no configuration needed” line for Polls/Stickers/Collab Doc/Collab Whiteboard; link each extension guide (fixes 5 pages at the source).
  2. ai-assistant-chat — add AI-Agent Dashboard-setup prerequisites callout (completely unreferenced dashboard dependency).
  3. Calling components (call-buttons, incoming-call, outgoing-call, call-logs) — add upfront prerequisites callout → calling-integration + call-features.
  4. message-header / message-list / message-composer — link AI props → ai-features, extension attachments/translate → extensions.
  5. call-features → link calling-integration; calling-integration → link the standalone call component pages.
  6. Add bidirectional event-system ↔ guide links (block/unblock, message-privately, threads, group-created) and link component “Events Received” tables → event-system.