First, it would be extremely helpful to have the ability to reorder individual key-value pairs after adding them. It’s frustrating when columns are scattered throughout the list, making it harder to maintain structure. A simple drag-and-drop feature—perhaps using an icon on the left—would make organizing them much more convenient.
Second, adding new key-value pairs feels unnecessarily cumbersome at the moment, as it requires scrolling all the way to the top each time you want to add another rule. A more efficient approach would be to allow pressing the Tab key to automatically create a new rule below the last one, enabling a much smoother workflow.
I hope you’ll consider these two relatively small improvements, as they would make a significant difference in terms of developer experience (DX).
I wanted to highlight this post because I genuinely believe this part needs a redesign. Working with 30+ fields isn’t unusual, yet it quickly becomes a hassle—especially when I have to manually sync insert and update statements for every minor change.
One of the most frustrating aspects is the lack of a clear indicator for missing key-value pairs. A highlighter that visually marks which columns haven't been included yet would be incredibly helpful, allowing me to instantly spot omissions or duplicates.
Beyond that, and touching on a broader security discussion, I think the ability to automatically generate key-value pairs based on form data would be a game-changer. If that process could be reliably synced, it would be a huge time-saver and reduce the risk of human error.
"Why not just use raw SQL?" you might ask. Well, it comes with its own risks—such as accidentally updating all rows if you mistakenly comment out a WHERE clause in an UPDATE statement. That leaves us with two options: manually handling key-value pairs or accepting the entire form input, which is simply not an option from a security standpoint.
Ultimately, I hope this sparks further discussion and exploration. At its core, this feels like a UX issue—one that, if solved, could make development significantly smoother.
Thanks!