Please add the ability to use new {% content_for “blocks” %} inside a theme-app-extension (app block).
18:03:44 │ theme-app-extension │ Error while updating drafts: [blocks/wrapper.liquid] Liquid syntax error (line 2): Unknown tag 'content_for'
Thank you!
Thanks for the feature request - I’ll raise this to the Online Store team 
Thank you very much!
The main idea would be to have an app block wrapper with multiple nested app blocks.
The sections/apps.liquid liquid is pretty limited, and even for apps with theme_write access, it is challenging to help merchants with theme upgrades since the custom sections are not carried over.
The app block wrapper could solve this for many apps.
Hey @Liam-Shopify , any news about this feature request regarding nested app blocks?
I really want my best for my app customers and having the ability to nest app blocks (or at least add private blocks) would keep the merchant building in the Theme editor.
Now, I either have to:
A. Improvise some sort of section builder in the app which will likely be odd and have a bad UX. Not to mention storing the data.
B. Or, push custom code (sections or theme blocks) into the current theme which I really don’t want to, but would be the best way to keep merchants in the Theme Editor and build there.
C. Rely on App blocks but use custom CSS selectors to identify and “connect” app blocks and combine them. It keeps the merchant in the Theme editor and I don’t need to push custom code into the current theme. But it still is a bad user experience for the merchant since they need to use developer tools.
So in the end having this feature would definitely make merchants happy, but also developers.
I understand why App Block limitations were added a couple of years back, but I don’t believe they’re needed anymore. It’s a different era.
Thanks a lot!