Nice idea. Can the result be a single form which does both insert and update? That’s my way of working now so I only do forms once and it’s just one to make changes to in the future.
We combine update and delete Actions, ie, if a checkbox is ticked to confirm delete, a condition within the Server Action for the update is run to execute the conditional delete Action. Saves doubling up on Actions and eases the workflow.
Wow! I was wondering about it some days ago! A basic CRUD with a grid to show data with delete, update and insert buttons. Almost like scafold on Ruby on Rails.
This is a great idea indeed. Now imagine if you have a option in that CRUD too to allow you to connect your API endpoints that’s manage your user registration and social login or payment gateways. Let’s say you have the option to connect a Auth0 or Stripe API endpoint at each CRUD step.
I’d love to see enhanced support for the different http methods so the APIs can follow best practices out of the box. POST for create, PUT for mods, GET To retrieve, etc.
Well although the different HTTP methods might be more standard for REST API calls , Server Connect usually handles data posted by html forms. Like when you have form for insert or update records to the database.
Those HTML Forms always post data as GET or POST only. You can’t post form data as PUT method.
So for own processing of your forms and data in Server Connect it doesn’t make much sense to support other methods. Unless you are exposing your Server Connect API to other external sources that use it as REST API only.