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
I think it makes sense to also add the pooling for stores. The main reason to have the pooling was to reduce the number of updates/renders. If we now start moving properties and logic to stores - they will call the "requestUpdate" more often than before because it is not pooled.
@quarkus not if the updates are comming from the same property. Pooling works across multiple properties on the element. The store is only one property on the element. When the store has multiple properties as well and those are not pooled (in the store) multiple changes inside the store will trigger mutliple upldates on the element.
May be it makes sense to pool Updates in Stores just like we do in the Base Element.
Maybe this is not needed once we can have Store in Stores ..
The text was updated successfully, but these errors were encountered: