You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Renaming a NoNode-ed COMP requires uncook-recook #49
hmm so an OP's .id attribute doesn't change between renames... 😃 but it does if you move it somewhere else
and since extensions reinit when a comp is moved, maybe I can just cache this id instead of the reference to the clearly non-existent ghost OP after a rename
Activity
[-]Renaming a QuickExt-ed COMP requires re-init[/-][+]Renaming a QuickExt-ed COMP requires uncook-recook[/+]function-store commentedon Oct 28, 2024
hmm so an OP's .id attribute doesn't change between renames... 😃 but it does if you move it somewhere else
and since extensions reinit when a comp is moved, maybe I can just cache this id instead of the reference to the clearly non-existent ghost OP after a rename
[-]Renaming a QuickExt-ed COMP requires uncook-recook[/-][+]Renaming a NoNode-ed COMP requires uncook-recook[/+]