Writing good component API

When it comes to React components, props are the API that developers consume.

A good API should be obvious, something the developer can guess. You want to make it easier for the developer to implement their feature and move on. This is valid not just for developers creating component libraries, but also for developers building applications. Your team mates have to use the component API you create.

This series is inspired by the talks and articles of Sebastian Markbåge, Brent Jackson, Jenn Creighton and A. Jesse Jiryu Davis

• 1. Don't create 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. 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.
• 4. Beware of the Apropcalypse!
  It's all fun and games when you just one more tiny prop but suddenly you're drowning in props!!
• 5. 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?
• 6. Establishing a relation between components
  The combination of the dot syntax and context can make a component smart while keeping composition intact at the same time.
• 7. Surely, there's more?
  TODO