Hi,
We implemented this part of an optimizely article to expand multiple levels of nested ContentArea property. We plan on making this our default way to fetch data from the content delivery api:
https://docs.developers.optimizely.com/content-management-system/v1.5.0-content-delivery-api/docs/customizing-conversion-from-icontent-to-contentapimodel#example-expand-multiple-levels-of-nested-contentarea-property
Now we found an issue with this approach when there is a circular reference in the hierarchy of the fetched data. Where for example:
'A ' contains a content area, inside of it is a content called 'B' that references back to 'A' in it's own content area as well.
From this we get a circular reference which would crash the application.
Any suggestion to help detect a circular reference when it happens to solve this issue?
Thanks in advance.