@nivaro/react 0.1.243 → 0.1.245

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.ts CHANGED
@@ -3827,12 +3827,26 @@ export declare function RecordGridWidgetBody({ widget }: {
3827
3827
  widget: PageRendererWidget;
3828
3828
  }): JSX.Element;
3829
3829
 
3830
- export declare function RecordReadView({ collection, itemId, layoutData, flush }: {
3830
+ export declare function RecordReadView({ collection, itemId, layoutData, flush, renderSlot, integrityMarks }: {
3831
3831
  collection: string;
3832
3832
  itemId: string;
3833
3833
  layoutData: ReadViewLayout;
3834
- /** Host already pads and scrolls the body (the record form's read mode). */
3834
+ /** Host already pads and scrolls the body (the record form's Summary mode). */
3835
3835
  flush?: boolean;
3836
+ /**
3837
+ * Page-slot sentinels (`__comments__`, `__tasks__`, …) the host wants to
3838
+ * keep LIVE inside the read view — Summary mode is read-only for the
3839
+ * record's fields, but notes and tasks stay editable (Rob). Return null to
3840
+ * skip a slot. A slot placed in a section renders inside that card; the
3841
+ * rest render full-width under the cards, in layout order.
3842
+ */
3843
+ renderSlot?: (key: string, assignment: LayoutAssignment) => ReactNode;
3844
+ /**
3845
+ * Summary mode hides the data-integrity banner but must not hide the
3846
+ * problem: with this on, every field (or child grid) that carries a
3847
+ * finding gets an amber mark whose tip lists the messages.
3848
+ */
3849
+ integrityMarks?: boolean;
3836
3850
  }): JSX.Element;
3837
3851
 
3838
3852
  /**
@@ -3840,8 +3854,9 @@ export declare function RecordReadView({ collection, itemId, layoutData, flush }
3840
3854
  * watermark and, when other people changed the record in between, renders a
3841
3855
  * one-line recap above the form. The server owns the session semantics (a
3842
3856
  * refresh within 30 minutes keeps the same baseline), the strip just shows
3843
- * whatever the touch returned. Dismiss is per-mount — the next genuine visit
3844
- * recomputes against the new baseline anyway.
3857
+ * whatever the touch returned. Dismiss POSTs /dismiss, which collapses the
3858
+ * server baseline to now — a reload inside the session grace stays quiet, and
3859
+ * only changes made after the dismissal come back as news.
3845
3860
  */
3846
3861
  export declare function RecordRecapStrip({ collection, itemId }: {
3847
3862
  collection: string;