This is very important! No, not like that. This is super, mega, incredibly important!
And here's why:
The fact is that often when developing complex applications, the structure of the application becomes neurotically ponderous. If you don't structure it, it becomes very difficult to work with it. Now many people use the section elemet for this purpose. But this misuse creates an additional burden that could easily be avoided if it were possible to use the comments that Wappler sees.
This situation is particularly acute when developing SPA, PWA, and mobile apps, Since all the key elements are placed on the same main page.
What need:
- Element of the normal
comments. It is displayed as a self-contained element in the app structure. Its properties display the content of the comment. In the code, this is a normal string comment. - The element
comments-section. In the app structure, you can place any other app elements inside the element and collapse it to hide it when working (just like sections are working now). Its properties display the content of the comment. In code, these are two lowercase comments (beginning and end) that frame a piece of code that goes inside an element in the application structure.
Given the benefit of this in development compared to the ease of implementing this feature it can be given the highest priority