[bug] Nested instance replaced inside an instance is reset when the main is edited; swap_instance refuses nested instances #11
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Expected: A nested instance swapped or replaced inside an instance (e.g. a badge inside a row component) keeps that override when the row's main component is edited later.
Actual:
swap_instanceon the nested badge fails with "not a component instance root".write_htmlmodereplaceon that nested badge works at first. But any laterupdate_styleson the row main (for examplegap) re-syncs the instance, and the nested badge goes back to the main's badge.<x-paper-clone>of a frame holding such rows also drops the replacement.Repro: 1) Make main
Rowholding an instance ofBadge / Greenwith Label "OK". 2) Place an instance ofRow. 3)write_html {mode:"replace", targetNodeId:<nested badge>, html:'<x-paper-instance component="Badge / Amber" overrides=\'{"Label":"Late"}\'/>'}. 4)update_styleson theRowmain{gap:"0px"}. 5) The instance showsBadge / Green"OK" again.Workaround: Take the badge out of the row component and place it next to the row instance inside a wrapper frame.
Impact: Status overrides inside list rows are lost silently, with no warning.
Filed from PaperCraft 0.7.2 (macos).