Smart compose about recompose

[acdlite]

See #182 for a potential solution to this problem

[acdlite]

We address this in part using our custom version of createElement(), which avoids unnecessary intermediate React elements by detecting referentially transparent function components. This only works with certain helpers like mapProps() — helpers that use lifecycle methods, context, etc necessarily require a class component.

So there's only so much we can do here. Better documentation and examples that illustrate best practices is needed.

For example, instead of using two sequential mapPropsOnChange(), use a single mapPropsOnChange() and compose the mapping functions together.

Instead of multiple withState(), use a single withState() or use withReducer().

Or if your component is sufficiently complex and the extra elements concern you, then perhaps Recompose isn't the right fit for that particular component and you should use a regular class instead.