The question is how would this affect the usability in the UI. Initial this limitation was added to Gentics Mesh since we have had a bad experience with deeply nested structures in Gentics CMS. Not sure whether this point is still valid.
GraphQL type provider might need to be adapted as well in order to allow accessing the nested fields.
Might be as simple as removing these kinds of checks:
For List fields: https://github.com/gentics/mesh/blob/221e06d49c13daa5afda8d15181c0db4b49d5887/core/src/main/java/com/gentics/mesh/core/data/node/impl/MicronodeImpl.java#L195
For Micronode fields:
The question is how would this affect the usability in the UI. Initial this limitation was added to Gentics Mesh since we have had a bad experience with deeply nested structures in Gentics CMS. Not sure whether this point is still valid.
GraphQL type provider might need to be adapted as well in order to allow accessing the nested fields.