Rewrite readme mixin example to use Higher Order Component
See original GitHub issueHello, I see the readme demonstrates how to build a form element. However it utilizes the mixins
field.
Now that mixins are considered harmful would a rewrite of the example in the readme be welcome?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:27
- Comments:9
Top Results From Across the Web
Higher-Order Components - React
In this document, we'll discuss why higher-order components are useful, and how to write your own. Use HOCs For Cross-Cutting Concerns. Note. We...
Read more >Higher Order Components in React - SitePen
In the simplest terms, a higher-order component is a function that accepts a component, and returns a new component that wraps the original....
Read more >Higher Order Components · react-indepth - DevelopmentArc
This function generates and returns a new Component, which is a wrapper around the passed in Component(s). The need for HOC came about...
Read more >Mixins Are Dead. Long Live Composition | by Dan Abramov
A higher-order component is just a function that takes an existing component and returns another component that wraps it. }); return StoreConnection;
Read more >Higher-order Components - gists · GitHub
I created two packages which you can use for creating of high-order components. With react-provide-props you can easily create high-order component which will ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
With the announced changes in v16 this will become a more pressing topic https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html
@Jareechang I’d submit a quick PR and link here a gist. I’m sure 20 other folks would appreciate it even if the maintainers choose never to change the readme. Sadly I’ve lost the context I had when I opened this issue 😛