Skip to main content
New to wireframes? Start with UI Customization Concepts and the Template Variables overview.

Overview

The Inline Comments Section wireframe exposes the variables below. Use them inside any <velt-inline-comments-section-...-wireframe> tag via three forms: All variables are mapped — reference them by their short name. You do not need the componentConfig. prefix.
Naming conflicts — use full path. A few names collide with mappings used elsewhere. Inside an Inline Comments Section wireframe, prefer the explicit path on the right when reading these values:
The list iterates through the standard Comment Dialog primitives — see Comment Dialog Wireframe Variables for variables that resolve inside nested dialog tags.

App State

App-wide values resolved from the shared signal.

Data State

Per-section data: the live annotation list, the in-flight composer annotation, and available statuses.

UI State

Per-instance UI flags driven by the section itself.

Feature State

Capability flags toggled via SDK config.

Common Props

Every Inline Comments Section primitive accepts: Signal inputs (for parent-child component composition):
  • [componentConfigSignal] — shared per-section config signal (annotations, statuses, filter / sort state).
  • [parentLocalUIState] — per-instance UI state signal.
The root <velt-inline-comments-section> element additionally accepts attributes that map onto config and local UI state values: target-element-id, folder-id, document-id, location-id, context, dialog-variant, composer-variant, composer-position, comment-placeholder / reply-placeholder / composer-placeholder / edit-placeholder, multi-thread, full-expanded, read-only, message-truncation, message-truncation-lines, dark-mode, variant, shadow-dom.

Context-Specific Variables

These are only resolvable inside the nested wireframe tags noted in the Available in column. Each is injected by the iteration primitive that owns the tag.

Type Reference

Types referenced by the variables above are documented in Data Models:

Subcomponents

Each subcomponent below has its own wireframe tag.

inline-comments-section (root)

The customer-facing root primitive customers place in their app.
  • Public element: <velt-inline-comments-section>
  • Wireframe tag: <velt-inline-comments-section-wireframe>

inline-comments-section-panel

The wrapper container for the section. Composes header (count + filter + sort) + list + composer.
  • Public element: <velt-inline-comments-section-panel>
  • Wireframe tag: <velt-inline-comments-section-panel-wireframe>

inline-comments-section-skeleton

Skeleton loader.
  • Public element: <velt-inline-comments-section-skeleton>
  • Wireframe tag: <velt-inline-comments-section-skeleton-wireframe>

inline-comments-section-comment-count

The “N comments” label at the top of the section.
  • Public element: <velt-inline-comments-section-comment-count>
  • Wireframe tag: <velt-inline-comments-section-comment-count-wireframe>

inline-comments-section-list

Iterates annotations and renders a comment-dialog primitive per entry. Inside, the standard Comment Dialog Wireframe Variables resolve.
  • Public element: <velt-inline-comments-section-list>
  • Wireframe tag: <velt-inline-comments-section-list-wireframe>

inline-comments-section-composer-container

The per-section composer (renders the standard comment-dialog composer). Inside this wireframe the standard Comment Dialog Composer variables are available.
  • Public element: <velt-inline-comments-section-composer-container>
  • Wireframe tag: <velt-inline-comments-section-composer-container-wireframe>

Deeply-Nested Wireframe Tags

The filter and sort dropdowns decompose further. Each tag below has its own <velt-inline-comments-section-...-wireframe> registration and inherits context variables from its parent dropdown.

Filter dropdown tags

The filter dropdown lets the user filter the section by status. Composes trigger + content (with apply button) + per-status list-items.

Sorting dropdown tags

The sort dropdown — pick between “Created first”, “Last updated”, “Most replies”, etc. Composes trigger + content + per-option content-items with tick / icon / name.