(If you are a representative of an upstream for which there exists an image and you would like to get involved, please see the Maintainership section below!)

Also, the chances of breaking something are really high, because not even you remember how the code actually works.

This does work, but as can be seen in the PR, it raised serious concerns over the maintainability of the resulting schema due to all of the duplication.

From my point of view, this approach will help you to write cleaner code. Also, it will help to maintain the project. For instance, moving a file from the current directory to another will cause fewer problems, because every file uses an absolute path instead of a relative one. Last but not least, it helps you during development.

Scalability is the problem you want to have, and sooner rather than later, but maintainability is the problem you’re definitely going to have, sooner or later.

Your code will much more maintainable and your designer (or your inner designer) will thank you.

If you are working in a large enterprise application, we have to create small components. Small components are much more flexible in terms of reusability and maintainability.

This simplifies maintenance and keeps things clean by allowing related code to be grouped before inclusion elsewhere.

Maintainable code is code that you don’t need to modify when the browser changes.