Bugfix when complex structures have to be displayed in the frontend.

Problem:

when creating complex structures with sub shacl nodes with higher depth some data of nested shapes were not displayed in the frontend when the shape was uploaded. Example: --> Error message "The shape does not exist in the file". It is definitely existing.

Solution:

The frontend code processed the shapes in the order as they came back from the backend. However sub structures were not setup correctly if a parent shape was processed before a child shape. The solution was to introduce a sorting of the shapes returned by the backend. Sort order is the depth of the shape inside the tree, starting from high depth (leafs) to no depth (root). Screenshot of fixed example:

@moosmannp Would you be so kind to review this one as soon as possible? Project partners need this functionality to create their claims.