Sitecore Marketplace :: Custom field parent/child components limitation

I have been working with Sitecore Marketplace since it was released, built a couple of custom fields, some for work and some for run, if you have not seen my previous blog post, here is the link for it, in which I show how to create a custom field for image selector from lytho DAM, and how you can add it to your datasource template; while doing that we ran into a case where we see a limitation and working with Sitecore team to register a feature request; if you're intrested keep reading. 

If you went through my previous blog post, you know that we build a custom field for image selection from lytho DAM, while this is working perfectly for simple components where we have a direct data source with out custom field as you can see below: 

You would notice from the above screenshot you can easily see the fields of the selected component datasource on the right panel, nice!, I can click open app and use my custom field, BUT wait we had another case where we're using a parent childs component in such case we couldn't get the child datasource fields to show on the right side panel, see below screenshots: 

As you can see from the above, I can get into the parent datasource only, we can't reach out to the child datasource in order to get into its datasource fields. hmmm...!

That limitation has no solution up to the moment using marketplace SDK, but what could be workarounds or solutions we can use, here are some suggestions: 

1. A custom button on the image field as example where on click it does same thing as "Open App" button for the custom field
2. Change the way we build the Parent/Childs components and utilize the old way of dynamic placeholders and adding the childs 1 by 1, side effects; will be loosing the manage items from above screenshots, and having more renderings added to the page presentation details. but, you will be able to access each child datasource fields this way... 

If you can think of any other solution for this limitation or you have ran into the same issue and you figured out some how, feel free to comment out on this article or do reach out, will adjust the article and add your solution!