At first, you might be wondering why you should ever create your own components. Especially when you look at those extensive sets of readymade components in the Trinidad, Tobago, and Tomahawk project, you might wonder why there is still a need to create your own composition components. The reason is simple—no one but you can create a component that exactly fits your needs and application. This means that you often have to combine different components, validators, and converters.
Combining is not a problem, but what if you have to make the same combination of components a couple of times? Then you’re breaking the DRY principle; you are repeating yourself! We will look at the login page of the MIAS system as an example. As this is a rather simple page with a very limited number of fields, the benefits of using composition components are perhaps not that clear to see in this example. But imagine if the page is twice as large and you have dozens of pages...