As I am getting deeper and deeper into more complicated applications I am finding that I often land up breaking the App Structure panel because I am removing the classes it needs in order to display it correctly.
The reason I remove the classes is because of creating content management systems for my end users to have the greatest possible control over their design layouts.
Here is a really silly and simple example.
<div class="container"></div>
This would show up in the App Structure panel correctly, however what if I wanted to allow my end user to create fixed width or fluid width containers via their CMS, then I would alter this to obtain the class needed from the database.
<div dmx-bind:class="db-container-type"></div>
This works great but breaks the App Structure panel in Wappler.
I wonder how many other users run into a similar situation pretty often and if there would be a way for Wappler to work around this. Maybe a false class that is only read by Wappler internally like
<div dmx-app-structure="container" dmx-bind:class="db-container-type"></div>
Would love to hear some other users experiences with this same sort of issue of breaking the App Structure Panel on purpose, but having no real alternative.
Last updated: