-
1. Re: Feature Request: Named web app items
cristinel@adobe Jul 9, 2014 1:27 AM (in response to Liam Dilley)Hi Liam,
Named web app items will be probably bee looked at, but it's not a top priority compared to the other items to be completed or fixed on liquid and new module syntax. We are pretty much aware of this request as it also surfaced up with the Open Admin release (when we did named web apps).
Kind regards,
Cristinel
-
2. Re: Feature Request: Named web app items
Liam Dilley Jul 9, 2014 4:17 AM (in response to cristinel@adobe)Thanks, As I mentioned in another thread.
I am just trying to find options to avoid multiple web app calls where your running if conditions etc and you want a different bit of content.
If you have a web app with several web app items you can render a different item based on different conditions your only using one web app module. This is more efficient then using 6 content holders (which do not have the advantage of the custom fields (my components app does fill that gap mind you) )
I know you guys are looking to increase the module limit further but I want to look to be more efficient with the liquid and rendering and show others how to be efficient with their code.
This is more my cup of tea coding a site and I want to have little or no repetition, reusable elements and efficient features So being able to render different web app items based on filters and names, being able to control the way a web app list renders based on similar things is high on my agenda for development.



