Home >Web Front-end >JS Tutorial >How to use Vue high-order components
This article mainly introduces the use of exploring Vue high-level components. The editor thinks it is quite good, so I will share it with you now and give it as a reference. Let’s follow the editor to take a look, I hope it can help everyone.
High-order components (HOC
) are common vocabulary in the React
ecosystem. The main way to reuse code in React
is to use high-order components. components, and this is also the officially recommended approach. The main way to reuse code in Vue
is to use mixins
, and the concept of high-order components is rarely mentioned in Vue
. This is because in # Implementing high-order components in ##Vue is not as simple as in
React. The reason is that the design ideas of
React and
Vue are different, but they are not It is said that high-order components cannot be used in
Vue, but the benefits brought by using high-order components in
Vue are not qualitative compared to
mixins Variety. This article mainly explains the implementation of
Vue high-order components from a technical perspective, and will analyze it from both the perspectives of
React and
Vue.
Starting from React
At firstReact also used
mixins to complete code reuse, for example, to avoid components For unnecessary repeated rendering, we can mix
PureRenderMixin in the component:
const PureRenderMixin = require('react-addons-pure-render-mixin') const MyComponent = React.createClass({ mixins: [PureRenderMixin] })Later
React abandoned this method, and then Use
shallowCompare:
const shallowCompare = require('react-addons-shallow-compare') const Button = React.createClass({ shouldComponentUpdate: function(nextProps, nextState) { return shallowCompare(this, nextProps, nextState); } })This requires you to implement the
shouldComponentUpdate method in the component yourself, but the specific work of this method is
shallowCompare will help you complete it, that is, shallow comparison.
React In order to prevent developers from always writing the same code in components, it is recommended to use
React.PureComponent. In short,
React In a step-by-step separation from
mixins, they believe that
mixins is not a good model in the
React ecosystem (note: it does not say
mixins Not good, only for the
React ecosystem), the views are as follows:
mixins brings implicit dependencies
mixins and
mixins,
mixins and components can easily lead to naming conflicts
mixins is intrusive, it changes the original component, so modifying
mixins is equivalent to modifying the original component. As the demand grows,
mixins will become complex, leading to snowballing complexity. .
HOC is not a silver bullet. It naturally brings its own problems. The point is: using ordinary components with
render prop can do anything that HOC can do.
mixins and
HOC, just like technology itself is not good or bad, only whether it is suitable or not. Isn’t it the same for these two buddies
React and
Vue?
The above is the detailed content of How to use Vue high-order components. For more information, please follow other related articles on the PHP Chinese website!