Question: `lifecycle` and server-side rendering? about recompose

[acdlite]

Not sure about this. If you need to use componentDidMount() or any of the other component lifecycle methods, at that point you should probably use a class component.

[lukewestby]

Thanks for the response, and I totally understand if you don't want to include this feature at the moment, but just for discussion now:

This library covers most of the useful Component API surface, which I think componentDidMount() is in at least in the case that I mentioned, and its stated intention seems to be to eliminate the need for extending Component or calling React.createClassin favor of functional style, so I guess I'm having a hard time understanding why componentDidMount() would not qualify. Could you explain why you think componentDidMount() is better handled by extending Component?

[istarkov]

IMHO:
The most common case in componentDidMount is to use refs for component Dom events, for jQuery plugins like integration,
(the other case is for events like resize)

But internal refs for stateless component is gone every new render, (and stateless component doesn't have each own ref) so it's impossible to use this common case.
Also how to access internal component refs without some hackable api?

[lukewestby]

I definitely see where you are coming from and agree when it comes to using refs. Another example that I have frequently encountered, however, is for components that need to update state on window scroll events for some visual effect, virtualization purposes, etc. In these cases refs haven't been necessary but I do need to call window.addEventListener() on the client. I get that this use case might be too specific to warrant inclusion in the library itself. It would be totally fine to write a custom HoC and use compose() -- excellent API design, btw 😄

Thanks!

[acdlite]

I'm hesitant to add support for other lifecycle methods because lifecycle methods usually need to call setState() or save references to a subscription on the component instance. Both of these go against the functional nature of Recompose's API. I'm still not sure if the existing lifecycle() helper shouldn't be removed.

I'm going to close this issue, but if you have an idea for an API, please let me know :)