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
Currently, thecreateContainer provides an ability to do some cleanup on a per-container basis. It is also possible to create a single store instance shared among a number of containers and know when each of them is destroyed.
const Container = createContainer(Store, {
onCleanup: () => {
// This is run for every container that gets destroyed.
}
});
Then when rendering we can do;
<Container scope="my-scope"> ... </..
We also know that by design RSS destroys the store when there are no more containers left in a given scope (for this case my-scope). Currently there is not an integrated way of knowing when the store is destroyed. This can become necessary for example to abort all ongoing requests.
As a solution consider;
const Container = createContainer(Store, {
onDestroy: () => {
// This is run when the store is destroyed.
}
});
Or there may be alternatives where we can 'deduce' when to do the final cleanup, for example providing number of containers left as a prop to onCleanup etc.
The text was updated successfully, but these errors were encountered:
This is now supported as part of the improved Store/Container API #198 .
Basically by using the new containedBy attribute on store creation we also support handlers.onDestroy.
Currently, the
createContainer
provides an ability to do some cleanup on a per-container basis. It is also possible to create a single store instance shared among a number of containers and know when each of them is destroyed.Then when rendering we can do;
We also know that by design RSS destroys the store when there are no more containers left in a given scope (for this case
my-scope
). Currently there is not an integrated way of knowing when the store is destroyed. This can become necessary for example to abort all ongoing requests.As a solution consider;
Or there may be alternatives where we can 'deduce' when to do the final cleanup, for example providing number of containers left as a prop to
onCleanup
etc.The text was updated successfully, but these errors were encountered: