Created by: ArpegorPSGH
Addressed problem description
This solves issue #4607 (closed). I also solved what looked like an issue and slightly expanded the node functionality.
Solution description
I added list length matching at each level in the inputs, while not changing the node treatment on the lists. In the get_level function, it seemed to me that the case >2 should instead be >= 2, otherwise the treatment is not consistent when you increase the number of levels. Finally, I enabled the use of the choice option when there is 0 nesting in the data input lists.
Preflight checklist
-
Code changes complete. -
Code documentation complete. -
Documentation for users complete (or not required, if user never sees these changes). -
Manual testing done. -
Unit-tests implemented. -
Ready for merge.