How To Reuse React Elements | by Sabesan Sathananthan | Codezillas


Mixins, HOC, render props, and Hooks are 4 methods to reuse elements

Picture by Vlada Karpovich from Pexels
  • There may be an implicit dependency between the part and the mixin (Mixin typically is determined by the particular technique of the part, however the dependency just isn’t identified when the part is outlined).
  • There could also be conflicts between a number of mixin (comparable to defining the identical state subject).
  • Mixin tends so as to add extra states, which reduces the predictability of the appliance and results in a pointy enhance in complexity.
  • Implicit dependencies result in opaque dependencies, and upkeep prices and understanding prices are rising quickly.
  • It’s troublesome to shortly perceive the habits of elements, and it’s needed to completely perceive all of the extension behaviors that depend on mixin and their mutual affect.
  • The tactic and state subject of the part itself is afraid to be simply deleted as a result of it’s troublesome to find out whether or not mixin is determined by it.
  • Mixin can be troublesome to take care of, as a result of Mixin logic will ultimately be flattened and merged collectively, and it’s troublesome to determine the enter and output of a Mixin.


  • Scalability restriction: HOC can’t utterly change Mixin. In some eventualities, Mixin can however HOC can’t. For instance, PureRenderMixin, as a result of HOC can’t entry the State of subcomponents from the skin, and on the similar time filter out pointless updates by means of shouldComponentUpdate. Due to this fact, React After supporting ES6Class, React.PureComponent is supplied to unravel this downside.
  • Ref switch downside: Ref is reduce off. The switch downside of Ref is kind of annoying underneath the layers of packaging. The operate Ref can alleviate a part of it (permitting HOC to find out about node creation and destruction), so the React.forwardRef API API was launched later.
  • WrapperHell: HOC is flooded, and WrapperHell seems (there isn’t any downside that can’t be solved by one layer, if there may be, then two layers). Multi-layer abstraction additionally will increase complexity and price of understanding. That is essentially the most essential defect. In HOC mode There isn’t any good resolution.


  • Property agent Props Proxy.
  • Reverse inheritance Inheritance Inversion.

Property Agent

Reverse inheritance

be aware

const NavbarWithRouter = withRouter(Navbar);
const CommentWithRelay = Relay.createContainer(Remark, config);


Please enter your comment!
Please enter your name here