Comment by Filip Milovanović on How to manage long dependency injection list for composite pattern?

This question is very unclear - it would help if you provided some more context. From what I was able to gather, you're saying that the input data (the example you provided) is created by users through a UI, is unknown in advance, there's nesting involved, and that you need to turn that input into some sort of a data structure that you can work with. However, the input seems non-uniform (fields don't have the same names, the structure is not the same throughout for different cases), so it's hard to parse in an abstract/generic way, so your resolve function is tied to a specific use case?