@veltdev/sdk-staging 6.0.9-beta.1 → 6.0.9

package/app/models/data/notification.model.d.ts

@@ -301,6 +301,8 @@ export interface CrossOrganizationConfig {
  * @see specs/org-notifications-top15-document-window/spec.md
  */
 export interface UserScopedNotificationsConfig {
+    /** Whether user-scoped notifications are active. Defaults to `true` on enable; an explicit `false` disables (input/prop parity with `CrossOrganizationConfig`). */
+    enabled?: boolean;
     /** Max user-scoped notifications fetched. Default 25; clamped to [1, 200]. */
     limit?: number;
 }

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

@@ -1082,11 +1082,26 @@ export declare class CommentElement {
 
   /**
    * To accept comment annotation
+   *
+   * @deprecated Use {@link acceptSuggestion} instead.
+   *
+   * The legacy "comments-as-suggestions" flow. Writes the workflow status
+   * (`annotation.status = Accepted`) and does NOT change `annotation.type`, so a
+   * suggestion card accepted this way keeps rendering as a suggestion.
+   * `acceptSuggestion` writes `annotation.suggestion.status` AND flips `type` to
+   * `'comment'`, which is what retires the card.
+   *
+   * Still functional; no removal date is set. `approveCommentAnnotation` is a
+   * separate mechanism and is NOT deprecated.
    */
   public acceptCommentAnnotation: (request: AcceptCommentAnnotationRequest) => Promise<AcceptCommentAnnotationEvent | null>;
 
   /**
    * To reject comment annotation
+   *
+   * @deprecated Use {@link rejectSuggestion} instead. The reject half of the
+   * legacy flow — writes `annotation.status = Rejected` without touching
+   * `annotation.type`. See {@link acceptCommentAnnotation}.
    */
   public rejectCommentAnnotation: (request: RejectCommentAnnotationRequest) => Promise<RejectCommentAnnotationEvent | null>;