Blog
Avoiding deeply nested component trees
The Problem
When building frontends you will pass data from a parent component to a child component. Often the child component renders this data, but not the component passing it along. The child components have different data requirements than your current component. Then you add a new component, somewhere down your component tree. It has new data requirements, so you have to pass its data through all its parent components. On top of data, it might also need callbacks to provide interactivity. You also pass these through all parent components. You change a lot of files to add new functionality. With all the data passing the readability of your code also decreases. Overall the maintainability of codebase decreases. Code samples and more at Medium.comWritten by
Our Ideas
Explore More Blogs

Using OutSystems UI Components in the right way
Using OutSystems UI Components in the right way Using OutSystems UI Components in the right way can be a game-changer for developers who want...
Vanessa William

OutSystems – Versioning Control
OutSystems – Versioning Control There are two widely used methodologies for versioning code: the traditional Branching methodology, and the...
Vanessa William
Contact











