Repeat component not being hidden
@Erik Beuschau
Looks strange . We 'll have a look @Tom Ireland 👍 @Tom Ireland
@Jacob Kofoed - Just wondering how complicated a fix for this might be ? Ran into an issue where I could not update node content based on a key event due to the redraw of all elements because of the Repeat Key . If I update the Repeat Key to be used as intended with the repeat item 's unique id instead of generating a random number , this does update the node but results in duplicate content . There are probably a couple more workarounds e .g . shifting outside of a component 's empty slot for the time being or maybe even looking at saving data to a db , etc . , to allow for the content to be re -rendered based on stored data as opposed to memory but I just wanted to demo what I 'm running into just in case it 's useful in terms of a use -case . I did a short video ( <10 mins ) for you . No pressure here obviously , given that you all have higher priorities just now . Just curious as to how complex this might be to address . https://www.youtube.com/watch?v=h6gsr5Vy-gM
.jpeg/public)