{Viewer}: `{prop}` changed, but {Viewer} takes {it|them} only when the viewer is created. Nothing was applied and the viewer was NOT rebuilt - rebuilding it silently would throw away scroll position, selection and expansion. Give the component a `key` that changes when this must take effect, so the rebuild is yours and visible, or drive the instance through the ref.

Warnings reference › react.viewer.*.mountOnly.*

Identifier

react.viewer.*.mountOnly.*

Raised by

React adapter

Since

1.63.0

What happened

A React viewer component (kanban, gantt, KPI, chart, layout) was re-rendered with a prop the underlying viewer only reads at construction. The component applies every prop the viewer has a setter for, hands the rest to the viewer's bulk set-style method where there is one, and names what is left over. The component neither drops the change without saying so nor rebuilds behind your back - the key lists exactly which props were left unapplied, so two different stale props produce two different lines.

The fix

Give the component a key that changes when the new value must take effect, which makes the rebuild explicit and lets you keep the cost in view; or take the ref and drive the live instance's own API instead of re-rendering.

The smallest fix

<LatticeKanban key={boardId} ref={ref} columns={columns} />

Reference

Covered in full at the API reference.