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 }}
This repository was archived by the owner on Oct 16, 2024. It is now read-only.
When we remove an Item that is currently selected by a Selector,
the remove method calls 'reselect' on the affected Selectors
to hold a reference to the now defunct Item. (-> Selector creates placeholder Item)
// ..// Remove Item from Collectiondeletethis.data[itemKey];// Reselect Item in Selectors (to create new dummyItem that holds reference)for(constselectorKeyinthis.selectors){constselector=this.getSelector(selectorKey,{notExisting: true});if(selector?.hasSelected(itemKey))selector?.reselect({force: true});}// ..
And when we now try to remove the placeholder Item,
it won't work because the Selector needs to hold a reference to it.
This is an expected behavior, but it shouldn't cause a rerender on each 'placeholder' Item remove try.
🎯 Expected behavior
Doesn't remove required placeholder Item and create it again with a rerender as side effect.