Introducing a Reusable Component Prop

Our solution is much better than when we started. However, it only gets more interesting from here.

The use case to cater to in this lesson is very relevant in the real world. There’s a high chance that if we’re building some sort of component, then that component will also take in some specific props, i.e., they will be unique to the component.

The polymorphic component use case

Our current solution takes into consideration the as, children, and other component props, based on the as prop. However, what if we wanted this component to handle its own props?