Velt Comments Best Practices

Velt Comments Best Practices

Comprehensive implementation guide for Velt's collaborative comments feature in React and Next.js applications. Contains 87 rules across 13 categories, prioritized by impact to guide automated code generation and integration patterns.

When to Apply

Reference these guidelines when:

• Adding collaborative commenting to a React/Next.js application
• Implementing any Velt comment mode (Freestyle, Popover, Stream, Text, Page, Inline)
• Integrating comments with rich text editors (TipTap, SlateJS, Lexical)
• Integrating comments with the Apryse WebViewer for PDF/docx documents
• Adding comments to media players (Video, Lottie animations)
• Adding comments to charts (Highcharts, ChartJS, Nivo)
• Building custom comment interfaces with standalone components

Rule Categories by Priority

Quick Reference

1. Core Setup (CRITICAL)

• core-provider-setup - Initialize VeltProvider with API key
• core-authentication - Authenticate users before using comments
• core-document-setup - Configure document context for comments

2. Comment Modes (HIGH)

• mode-freestyle - Pin comments anywhere on page
• mode-popover - Google Sheets-style cell comments
• mode-stream - Google Docs-style sidebar stream
• mode-text - Text highlight comments
• mode-page - Page-level comments via sidebar
• mode-inline-comments - Traditional inline thread style
• mode-tiptap - TipTap editor integration
• mode-slatejs - SlateJS editor integration
• mode-lexical - Lexical editor integration
• mode-canvas - Canvas/drawing comments
• mode-lottie-player - Lottie animation frame comments
• mode-video-player-prebuilt - Velt prebuilt video player
• mode-video-player-custom - Custom video player integration
• mode-chart-highcharts - Highcharts data point comments
• mode-chart-chartjs - ChartJS data point comments
• mode-chart-nivo - Nivo charts data point comments
• mode-chart-custom - Custom chart integration
• mode-apryse - Apryse WebViewer (PDF/docx) integration via @veltdev/apryse-velt-comments — ApryseVeltComments.configure(...).attach(instance), addComment({ instance }), renderComments({ instance, commentAnnotations }), durable TextEditorConfig anchors (text + occurrence + pageNumber)

3. Standalone Components (MEDIUM-HIGH)

• standalone-comment-pin - Manual comment pin positioning
• standalone-comment-thread - Render comment threads
• standalone-comment-composer - Add comments programmatically

4. Comment Surfaces (MEDIUM-HIGH)

• surface-sidebar - Comments sidebar component
• surface-sidebar-setup - Sidebar setup, display modes (embed/floating/page/focused-thread/fullscreen), filterConfig, groupConfig, sortOrder, V2 sidebar, navigation events
• surface-sidebar-v2 - Primitive-architecture V2 sidebar with 27+ composable primitives, unified filter model, and focused-thread view
• surface-sidebar-button - Toggle sidebar button

5. UI Customization (MEDIUM)

• ui-comment-dialog - Customize comment dialog
• ui-comment-bubble - Customize comment bubble
• ui-wireframes - Use wireframe components
• ui-autocomplete-primitives - Use standalone autocomplete primitive components to build custom autocomplete UIs without requiring the full VeltAutocomplete panel
• ui-agent-suggestion-primitives - 21 VeltCommentDialogAgentSuggestion* primitives for custom AI suggestion accept/reject UIs, resolution banners, header menus, and footer navigation
• ui-v2-primitives - Set defaultCondition={false} on V2 primitive sub-components to bypass SDK default show/hide logic when overriding sections in wireframe compositions

6. Data Model (MEDIUM)

• data-context-metadata - Add custom metadata
• data-comment-annotations - Work with annotations
• data-filtering-grouping - Filter and group comments
• data-activity-action-types - Use CommentActivityActionTypes constant for type-safe comment activity filtering instead of raw strings
• data-trigger-activities - Set triggerActivities on CommentData to auto-create activity records via POST /v2/commentannotations/add
• data-comment-annotation-data-provider - Use config-based URL endpoints on CommentAnnotationDataProvider without placeholder callbacks; additionalFields replicates fields to resolver while retaining in Velt storage; fieldsToRemove strips fields from Velt's DB for PII removal
• data-agent-fields-query - Use agentFields on CommentRequestQuery to filter getCommentAnnotationCount() to agent-tagged annotations; unread count equals total count when agentFields is set

7. Debugging & Testing (LOW-MEDIUM)

• debug-common-issues - Common issues and solutions
• debug-verification - Verification checklist

8. Moderation & Permissions (LOW)

• permissions-private-mode - Control global comment visibility with enablePrivateMode/disablePrivateMode and update per-annotation visibility with updateVisibility
• permissions-comment-saved-event - Subscribe to the commentSaved event for reliable post-persist side-effects (webhooks, analytics, external sync)
• permissions-visibility-option-dropdown - Enable the visibility dropdown in the comment composer to let users select public or private before submitting, and subscribe to visibilityOptionClicked events
• permissions-comment-save-triggered-event - Use commentSaveTriggered for immediate UI feedback (spinners, disabled states) on save button click — before the async database write completes
• permissions-visibility-routing - Use isAnnotationPrivate() utility for unified privacy checks across legacy iam.accessMode and new visibilityConfig.type (restricted, organizationPrivate)
• permissions-submit-in-flight - Use CommentDialogActionService.isSubmitInFlight(dialogInstanceId) to guard against duplicate submits in custom-actions sidebar hosts
• permissions-comment-interaction-events - Prefer past-tense event aliases commentToolClicked and sidebarButtonClicked over the present-tense originals in new code
• permissions-anonymous-user-data-provider - Register setAnonymousUserDataProvider() to resolve tagged contact emails to userIds at comment save time

9. Attachments & Reactions (MEDIUM)

• attach-download-control - Control attachment download behavior and intercept clicks

10. Configuration (MEDIUM)

• config-mentions-contacts - @Mentions, contacts, user assignment, autocomplete
• config-status-priority - Custom status and priority levels, resolve/update workflows
• config-reactions - Emoji reactions — enable, customize, add/delete/toggle
• config-attachments - File attachments — enable, upload, delete, allowed types
• config-text-formatting - Rich text formatting options in composer
• config-navigation - Navigation, deep linking, scroll-to-comment, shareable links
• config-dom-controls - Restrict comment placement to specific DOM elements
• config-sidebar-management - Programmatic sidebar data, filtering, and configuration
• config-sidebar-access-modes - Use accessModes filter in setCommentSidebarFilters() for privacy-based sidebar filtering (public/private)
• config-ui-behavior - UI/UX toggle methods — display, interaction, behavior (20+ methods)
• config-moderation - Moderation workflows — approve, accept, reject, read-only
• config-component-props - Typed props interfaces for VeltComments, VeltCommentDialog, VeltCommentsSidebar, VeltInlineCommentsSection — edit-mode placeholder overrides, assignToType, focus behavior

11. Wireframe Variables (MEDIUM)

• wireframe-variables-comment-bubble - Bind Comment Bubble + Comment Pin wireframe slots via {annotation.*}, {selectedAnnotationsMap[...]}, globalConfigSignal.featureState.*
• wireframe-variables-comment-dialog - Bind the ~110-slot Comment Dialog wireframe family (App / Data / UI / Feature State namespaces, comment / commentIndex loop-scope, root-level placeholder + unread-map paths, v1 aliases)
• wireframe-variables-comment-tool - Bind the Comment Tool wireframe via the flat-config {addCommentMode} / {commentToolEnabled} aliases and the canonical globalConfig.featureState.* / componentConfig.* paths
• wireframe-variables-inline-comments-section - Bind the Inline Comments Section wireframe ({annotations}, {skeletonLoading}, {filterState.*} / {sortState.*}, per-row loop-scope filter / sortOption / isActive / isAscending, featureState.* conflict-paths, nested Comment Dialog primitives in list + composer)
• wireframe-variables-multithread-comments - Bind the Multithread Comments wireframe ({nonDraftCommentsCount}, {minimalFilter}, empty-state + reset-filter gates, minimal filter / sort + bulk-actions dropdowns with isSelected loop-scope, data.user / uiState.shadowDom conflict-paths)
• wireframe-variables-autocomplete - Bind the Autocomplete @-mention picker wireframes (flat-config componentConfig.<path> access for flattenedItems / customGroupsEnabled / newUserContactError, loop-scope option / chip, option / group-option / chip / empty-state subcomponents, chip tooltip descendants)
• wireframe-variables-text-comment - Bind the Text Comment toolbar wireframes ({selectedWordsCount} / {selectedCharactersCount} / {position.*}, capability flags isUserAllowed / enableTextComments / rewriterEnabled, five conflict-name explicit paths)
• wireframe-variables-comment-sidebar-button - Bind the Comment Sidebar Button wireframe via flat-config (globalConfig.featureState.sidebarVisible, componentConfig.data.unreadCount / annotations.length, componentConfig.uiState.commentCountType / floatingMode)
• wireframe-variables-comment-sidebar - Bind the ~80-tag Comment Sidebar wireframe family — hybrid access (mapped focusedAnnotation / appliedFiltersCount / unreadCommentAnnotationCount alongside flat componentConfig.skeletonLoading / noCommentsFound* / virtualScrollData / filterConfig.*), loop-scope (focusedAnnotation, filter, item, group, tag), nested Comment Dialog scope in list / focused-thread / page-mode composer

Agent Comments — Critical API Reference

When the task involves AI agents creating comments or handling agent suggestion accept/reject, use these exact patterns:

Creating agent annotations — POST /v2/commentannotations/add:

data: {
  organizationId: "...",
  documentId: "...",
  commentAnnotations: [{
    type: "suggestion",                    // REQUIRED for Accept/Reject buttons
    commentData: [{
      commentText: "Finding text",
      from: { userId: "agent-id" },
      agent: {                             // On commentData[0], NOT annotation root
        agentSource: "external",           // "external" for non-Velt agents
        agentName: "My Agent",             // REQUIRED for external agents
        agentId: "my-agent",
        executionId: "run_123",
        reason: {                          // REQUIRED — finding details
          title: "Issue title",
          description: "Details",
          severity: "high",
        },
      },
    }],
  }],
}

Reading agent annotations — POST /v2/commentannotations/get:

• Use executionId filter for a specific run
• Use agentSuggestions: true for only pending (unaccepted) suggestions

Handling accept/reject on the client — use dedicated events, NOT commentSaved:

import { useCommentEventCallback } from '@veltdev/react';
const accepted = useCommentEventCallback('suggestionAccepted');
const rejected = useCommentEventCallback('suggestionRejected');

How to Use

Read individual rule files for detailed explanations and code examples:

rules/shared/core/core-provider-setup.md
rules/shared/mode/mode-popover.md

Each rule file contains:

• Brief explanation of why it matters
• Incorrect code example with explanation
• Correct code example with explanation
• Source pointers to official documentation

Compiled Documents

• AGENTS.md — Compressed index of all rules with file paths (start here)
• AGENTS.full.md — Full verbose guide with all rules expanded inline