Improving Class Input Usability for Better Workflow Efficiency

I think it would be much better if the class text input was a text-area that expands as we add more name classes. Many times, we need to change just one class, and we have to scroll left and right with the mouse, or we end up editing it in the code view. It’s a simple request, but I believe it could really help improve our day-to-day workflow.

CleanShot 2024-09-30 at 20.44.21@2x

This is an example of a class attribute with many class names inside.

<div class="d-flex w-100 justify-content-center mt-4 flex-wrap rounded rounded-3 border border-primary border-2 mt-3 pt-2">
1 Like

I do a lot of my work in code view, just find it easier. But if I were to follow the Wappler way (low code), then this would be a great asset.

1 Like

I totally get you, Ben, it's faster to use code view, but I work a lot with VSC, and when I switch to Wappler, I try to take advantage of its graphical interface.

On the other hand, compared to VSC, Wappler's code editor feels quite plain and lacks many features. It's a shame that you can't at least change the code's colors to your liking or add color themes like in VSC.

I could submit a feature request about the code editor, but I remember reading several requests about this topic in the community. :man_shrugging:

1 Like