I tried this recently to see how Wappler would do it, it was efficient but it uses snake case, instead of my preferred pascal case so that was a bit problematic. I know if I told it my preferred format then it would do it, but it would be better if the AI took into account the existing Wappler settings for this.
I'm in your camp, use AI a lot (both Wappler and external) but prefer to create my own Server Connects.
Notice the Unknown Action. This is where the signature is created as in
Claude has even created the necessary module code as in
I know that Brian could have easily produced a Wappler extension for this, but in the meantime, I have a working model.
Same goes for Word2HTML conversion that I had in place prior to Brian's excellent work. Needless to say, I will be using Brian's extension to replace what I presently have.
Problems:
I am limited to an average of 50 tokens per day. Could use many times that.
Need to keep an eye on what is being produced. Claude tends to make the odd mistake. Or maybe it's me giving the wrong instructions.
What I love: Claude thinks outside of Wappler within Wappler
Thanks Claude Sonnet 4. Using this I've fixed major critical issue in my user-login-server-action. I don't know how much we can trust AI for security and backend server actions, but I'm really happy that Wappler AI is kind of capable to create complex backend server actions.
I'm still very nervous about using AI for server connect scripts. I have very specific ways of working and I need to know exactly what it's doing and why. Plus, I think it's good practice to do all the server-side work yourself and Wappler makes this very quick and easy.
I will give it a try at some point, though. I'm sure it will prove useful if I'm not sure how best to achieve something and can benefit from AI's suggestions.