mirror of
https://github.com/multica-ai/multica.git
synced 2026-08-03 19:20:07 +02:00
The previous rerender passed the same `defaultValue` string, so React's dep-array equality short-circuited the sync effect entirely — the test only exercised the first-mount equality check, not the actual normalized-equal guard. Pass a different-but-trimEnd-equivalent value so the effect re-runs and the normalized-equal short-circuit is what keeps setContent uncalled. Co-authored-by: multica-agent <github@multica.ai>