Beat

Immutable.js 4.0 has been released two months ago (under MIT licence), might be worth upgrading. Also worth nothing that someone [mentioned an issue](https://github.com/immutable-js/immutable-js/issues/1514) over at immutable.js related to draft.js

Just my two cents after my third [smaller] project using the lazy generator. public example, albeit not large: https://github.com/bdurrer/calendarizator It's my own opinionated approach. I would go for more structure...

Here is sample node project, demonstrating the issue. Just run it with `node test.js`. [issue57.zip](https://github.com/HurricaneJames/react-immutable-proptypes/files/3106282/issue57.zip)

This issue is a duplicate of #53, which a few forks already fixed a year ago. Apparently this repo is dead, so if anyone reads this, just replace your dependency...

My workaround is to use the `allEffects` object. It seems to have the same information, in a different structure. A bit more complicated to inspect though.

@morzel85 In our case the warning was almost always right, these often were test errors. But you have to count the warnings and compare to how many you expect to...

We have a few tests on the main branch where the promise was just thrown away (stupid!). They timeout with a warning, but nobody noticed it for over a year....

Maybe displaying _all_ cached re-reselectors is not practicable anyway. I guess it could also have a negative impact on performance. At least in our setup, there are only a handful...

The behaviour is the same on windows. I _think_ that it happens when the dialog is presented while the timeout did not run out yet, but then the dialog stays...

This would be so nice to have, possibly even use the [sub]folder as a tag or metadata