I am trying to build my APIs in a more traditional manner. I pass the HTTP verb as a variable and keep all operations in the same API action.
I would like to use Wapplers built in validation, but on “GET” requests this will of course fail.
From the example below, the POST variable “name” is required and breaks the API call if not passed. The request is treated as GET if “operation” value is not present.
Does anyone have an elegant solution for issues such as these ?
Or will I just have to pass “fake” values along with the request (seems a little hacky)
In my experience, having separate SA for different verbs is a better appproach in Wappler.
If you try to conditionally put everything in a single end point, it will become very messy very quickly. And you will not be able to make use of the powerful server side validations - as you see with the name variable.
If you still want to continue down this path, just remove the require validation from name, and add a condition just after operation step to validate it.
In the operation condition you will have to add a response step to ensure SA exits after this “get” operation. Set query as value of response step.
