Writing good components

At the core of using React is writing components. React got really popular because of it's composition model. The contract with the framework is that we'd write good components and React will take care of the rest.

A good component is:

• 1. Doesn't have conflicting props
  When it comes to React components, props are the API that developers consume.
• 2. Give names to behaviors not interactions
  Naming event handlers is easy, until you put all your components together.
• 3. Follows the single responsibility principle
  It's all fun and games when you just one more tiny prop but suddenly you're drowning in props!!
• 4. Is composable - Just use children
  No, this isn't a post about child labour. It's a post about using children as props. Wait that doesn't sound right either. It's about composition, okay?
• 5. Is extendable - Order of props is important
  Welcome to the weird world of difficult to debug bugs because of order of props. This is part 3 of series about writing component API for great developer experience.
• 6. Is accessible
  TODO
• 7. Is easy to test
  TODO
• 8. Changes smoothly
  TODO