70
REST API direct integration needs support for PATCH method
H
Harri Sarsa
Currently, you can only configure a PUT operation for a REST API direct integration, which the
Update record
node then uses. Support both PUT and PATCH routes, so that if both are defined, the user can choose which method to use in Update record
.In the meantime, PATCH requests can be made with the
HTTP request
flow function.Log In
V
Valter de Brito
I also agree with the inclusion of the PATCH.
C
Csaba Gergely
I do also support adding PATCH method to the REST integration.
T
Thomas
+1 for PATCH method
Every database project I start becomes much more difficult because of the lack of a PATCH method. Is it really so difficult to implement this in AppGyver?
E
Enzo Matrix
+1 for Patch! Needed urgently
D
Dave Bibo
+1 for PATCH method
G
Gabriele Fusco
+1 for PATCH method
F
Felix
Firestore does not accept PUT, therefore PATCH is urgently needed to run Firestore and AppGyver together! See also:
T
Tim Stewart
Oops, I meant this as a reply to Eduardo, moved below.
E
Eduardo Jaramillo
HTTP request exposes the data on the server as anyone with access to the app can see the login details.
As is, the only (fairly easy) way is to GET the full record data, change whatever is to be updated, DELETE the old record and POST/PUT a new record with the new data. This approach has a drawback as the record may end up having a different id (if its assigned by the server).
T
Tim Stewart
Eduardo Jaramillo: I believe the patch would just use an authentication token in the header rather than plaintext authentication information (email/password);
Something like
"Authorization": "Bearer [AUTH_TOKEN]"
E
Erin Wagner
This would make a world of difference for what I'm building out. I'm going to have a lot more configuration to do with only PUT available.
Load More
→