Table of Contents

Class AnnotationBatchResult

Namespace
LMKit.Document.Annotations
Assembly
LM-Kit.NET.dll

The outcome of applying an AnnotationBatch: how many records each operation actually touched, plus per-record errors for the ones it refused (the caller's store stays dirty for those, so a refused change is re-offered, never silently lost). Canonical JSON shape: {"created":n,"updated":n,"deleted":n,"errors":[…]}.

public sealed class AnnotationBatchResult
Inheritance
AnnotationBatchResult
Inherited Members

Properties

Created

Records created.

Deleted

Records deleted.

Errors

Human-readable refusals ("update: unknown id 'x' on page 3", …).

Updated

Records updated.

Share