@veltdev/types-dev 6.0.17-beta.1 → 6.0.18

package/app/models/data/comment-resolver.data.model.d.ts

@@ -66,6 +66,13 @@ export interface PartialCommentAnnotationResult {
     } | null;
     originalData: CommentAnnotation | null;
     eventType?: ResolverActions | CommentResolverSaveEvent;
+    /**
+     * INTERNAL (SDK write path only, never sent to a resolver). True when `originalData` still
+     * carries `context.textEditorConfig.text` on purpose: the row is a legacy one whose resolver
+     * copy does not hold the anchor yet and this save is not a core event that hands it over.
+     * `CommonDbUtilsService` forwards it to the Velt-DB filter as `keepContextText`.
+     */
+    veltCopyKeepsContextText?: boolean;
 }
 export interface PartialTargetTextRange {
     text: string;
@@ -78,6 +85,22 @@ export interface PartialCommentAnnotation {
     };
     from?: PartialUser;
     assignedTo?: PartialUser;
+    /**
+     * The TipTap anchor text (`context.textEditorConfig.text`) — the highlighted sentence a
+     * text comment created through `@veltdev/tiptap-velt-comments` is attached to. Moved here
+     * from the annotation's `context` blob (which is otherwise customer-owned and stays in
+     * Velt) and merged back on read; the same PII class as `targetTextRange.text`. Present
+     * only when the annotation carries it (PM-2026-09-29-self-hosting-pii-egress-side-channels).
+     * When `context` itself is listed in `fieldsToRemove`, the WHOLE context object travels
+     * here instead.
+     */
+    context?: {
+        textEditorConfig?: {
+            text?: string;
+            [key: string]: any;
+        };
+        [key: string]: any;
+    };
     targetTextRange?: PartialTargetTextRange;
     resolvedByUserId?: string | null;
     [key: string]: any;

package/app/models/element/comment-element.model.d.ts

@@ -1394,8 +1394,8 @@ export declare class CommentElement {
   /**
    * To enable id-scoped anchoring for comment pins. When a pin's saved xpath is rooted at an
    * element id, that id is authoritative: the pin is placed only inside that element (on its
-   * saved child path, else on the nearest element under the id that still exists), and is not
-   * shown where the id is absent. New pins also skip framework-generated ids (React `useId`,
+   * saved path, else on the id element itself with the saved position percentages), and is not
+   * shown where the id is absent, duplicated or hidden. New pins also skip framework-generated ids (React `useId`,
    * Radix) when choosing the id to root at. Applies to existing pins. Defaults to disabled.
    */
   public enableIdScopedAnchoring: () => void;

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@veltdev/types-dev",
-    "version": "6.0.17-beta.1",
+    "version": "6.0.18",
     "description": "Velt is an SDK to add collaborative features to your product within minutes. Example: Comments like Figma, Frame.io, Google docs or sheets, Recording like Loom, Huddles like Slack and much more.",
     "homepage": "https://velt.dev",
     "keywords": [