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
Essentially, you must add loose: true to your [store.connect] definition, as the docs say:
By default, it is set to false, so updating model instances will not change items’ order or placement in the array. The typical use case to turn it on is when you have a paginated list, and updating or creating a model instance might affect the order or content of the list.
For the "memory-based" models (without the definition) this option is true. It would be a breaking change to switch it to true for custom storage, but I would re-think it. The case for setting it to false is that, otherwise, any change to any instance of the model will invalidate every list call - it might cause a cascade of fetches for pages of data. You can still control that then manually by calling store.clear(listModelInstance).
Thank you, I will clear the cache when adding/removing a model.
This solution works:
asyncfunctionsubmit(host,event){event.preventDefault();awaitstore.submit(host.draft);// clear cache for enumerable descriptors by this storestore.clear([Model]);if(!host.model){host.draft=null;}else{host.editMode=false;}}
example: https://stackblitz.com/edit/hybrids-store-ui-form-example-kbktry?file=src%2Findex.js,src%2Fcomponent.js,src%2Fmodel.js
The text was updated successfully, but these errors were encountered: