5 Patterns to make your React Components more useful

My apologies for the poor audio quality.

One of the things I love about React is how easy it is to encapsulate UI code into a component. I love this because it makes reuse of those components easy. But is it easy? I’ve made my fair share of components that had to accept a bunch of props to handle a growing list of different use cases resulting in a complex render function full of conditional statements and a confusing API for people using this “reusable” component. Eventually it becomes too much and I had to make a new version of the same component to handle slightly different use cases. Lots of code/bug duplication there because my reusable component wasn’t reusable enough.

There are patterns that have emerged in React that allow you to promote code reuse without sacrificing the simplicity or flexibility of the component. In this talk we’ll go over 5 of these patterns that will make your React components more useful.

[billpliske]

Holy cow, now I REALLY wish I had made this presentation ... this audio is rough.

[JoshSaintJacque]

For anyone having trouble listening to the audio, enable closed captioning - it seems to work fine.