Discussion Thread

Render a forum-style reply thread with controlled data and focus signals.

Host applications own the reply list and push updates via the replies signal. Tree navigation, view modes, collapse, and custom render regions ship in Phase 2.

  • Embedding a reply tree on a post detail page or review surface.
  • Building a headless discussion UI where the host controls persistence and transport.
  • Customizing meta/footer regions via Leptos slot children and events callbacks.
  • Hold replies in a RwSignal or server-backed signal and pass Signal::derive into replies.
  • Control focus with focus and set_focus for drill-in navigation.
  • Pass optional Leptos slot children for toolbar, empty state, composer, and reply regions.
  • Wire side effects through DiscussionEvents (on_submit, on_focus_change, etc.).
Sample design-review thread

Nested card thread with markdown, OP brand card, and viewer accent when current_user_id matches.

  • AC
    Alex Chen
    ·
    OP

    Main message with markdown and a design link.

    • SR
      Sam Rivera
      ··(edited)

      Agree — let's track open questions here.

      • JL
        Jordan Lee
        ·

        I'll draft the migration checklist.

        • PO
          Pat Okonkwo
          ·

          Depth-3 reply for tree testing.

    • MK
      Morgan Kim
      ·

      Separate branch at L1.

      • OA
        Orbital Agent
        ·
        Agent

        Based on the thread, the default depth is 4.

()()