-
-
Notifications
You must be signed in to change notification settings - Fork 634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement support for Inferno.memo ( React.memo ) #1443
Comments
great to learn Inferno is going to support it, could you share an estimated date if possible? |
Why will be all |
@chrkulbe Nothing is decided, there was discussion in Slack about dropping them. I recently did trial with this and we could maybe just add this functionality without any breaking changes |
Maybe an inferno supported library for this? Keep the core light. |
Hey @Havunen are there any updates on this? |
No, I have not had time to work on this. I personally have no need for this functionality so its pretty low on my todo list. Would you like to work on this? As suggested by @tamb it would make sense to have this as separate opt-in module. |
Yeah, I can give it a go! Would like to use inferno on a project but we use MUI, so memo support is necessary (according to #1510) I wont have time to grab this until early next week Thanks |
@PorterK FYI: Our implementation in Preact might be of interested as a starting point: |
Hmm, we could try out if Preact approach works for us? In infernojs we can add SCU hook on functional component too using |
Implement support for React.memo
Consider drop support for functional component hooks
onComponent
-API becomes useless after implementing this.https://reactjs.org/blog/2018/10/23/react-v-16-6.html#reactmemo
The text was updated successfully, but these errors were encountered: