I think it was mentioned that something like this might be included in Wappler at some point. I expect it might be quite a popular feature - which might be a good reason for including it.
Personally, I would prefer that the Wappler developers concentrated on features which are not already catered for by third-party programs. There are lots of features which are not yet included, or at least not documented. For Wappler to get the widespread interest and following it deserves, it needs to compete with lots of other frameworks (Angular, Vue.js, ReactJS etc., as well as the PHP frameworks). None of these (as far as I know) offer what you suggest, but I don’t think with any of them the reply to a question is never ‘this is not yet possible with xxx.js’). This reply appears quite often in the DMX forums - and probably applies still to Wappler. I don’t think people suggest that any of the other frameworks are lacking because they don’t manage the database side of things.
I think it would be a huge task to develop really good tools to manage all of the databases supported by Wappler (MySQL, SQLite, MS SQL Server etc.) - and such tools already exist. I use MySQL for websites and use Navicat to manage these databases. It’s excellent software. The same company develops software to manage many databases.
Also, should it be such a simple task to add a new field anyway, given you may need to consider type, length, indexes and other constraints? I think your suggestion is a little like suggesting that Wappler should incorporate image-editing software. Perhaps it could, however there is adequate third-party software available.