You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 21, 2021. It is now read-only.
Inferno adapter could replace the contents of the component with null which prevents its rendering.
It could then redirect methods which try accessing its internal props, state ... to the host node instead of the rendered nodes (which would be null).
I'm not sure about the implications to lifecycle methods though. Theoretically inferno unmounts a component once it returns null so I would suspect componentWillUnmount and/or componentDidMount not firing predictably.
Have to cross-check with preacts adapters
The text was updated successfully, but these errors were encountered:
Inferno adapter could replace the contents of the component with null which prevents its rendering.
It could then redirect methods which try accessing its internal props, state ... to the host node instead of the rendered nodes (which would be null).
I'm not sure about the implications to lifecycle methods though. Theoretically inferno unmounts a component once it returns null so I would suspect
componentWillUnmount
and/orcomponentDidMount
not firing predictably.Have to cross-check with preacts adapters
The text was updated successfully, but these errors were encountered: