there is no onCreate hook decorator

to write asyncronous code inside controller:

export default stateful( {
   render({ state, setState }) {
       return (<SomeComponent doAsynJob={ someFunc }></div>)
       function someFunc() { /* `state` here is the state when doAsynJob is initialized, not the actual state */ }
   } 
}

Here: https://gist.github.com/c570a5a3d60aa62d7918 gist, containing Tabs implementation with deku-stateful. It is working as is in deku 1.0. On Tabs first show - all works ok, but on second shown in the same place, we have { state } === undefined inside render fn. Looks like here we have same path (0.0.1.0.0.0.0), and it is destroyed onRemove inside stateful decorator.

Hi, in my use case I'm using deku-stateful to store local state for modal component. I'm attaching keydown and click events to the document on creation (support closing the modal on esc and when clicking outside) and storing the listeners inside the state in order to remove them when the component is being removed.

Currently, I'm not able to use deku-stateful because its not giving me the option to clean up this kind of resources on remove.

Thanks !

Demo fiddle: https://jsfiddle.net/montlebalm/m6mkac75/1/

I may be misunderstanding how this is supposed to work, but it seems like there's a bug with lists of components. Specifically, state is incorrectly preserved when a component is removed.

Try these steps in the linked example:

1. Click "Hit me!" on each of the counters to generate a unique count. For the sake of argument I'll assume the first has a count of 1, the second 2, and the third 3.
2. Click the "X" button on the first counter
3. Verify that there are now 2 counters and the counts are 1 and 2 respectively

I would expect the counts to be 2 and 3 given that we removed the first counter. It's easy to see that the path of the first counter remained the same, which means it inherited the state from the removed counter.