You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Airtable API provides two ways in which one can update a record, PATCH (not all fields) and PUT (all fields). I think deciding which type of operation to perform should be decided by the library and made abstract to library users.
I propose making 'patch' and 'put' (offered by the API, but not available in the library yet) private and creating a general 'update' function which decides which of these operation to perform.
This change appears to be feasible and not too time consuming.
The text was updated successfully, but these errors were encountered:
I was reading the docs for Airtable API and apparently now you can update all fields using a PATCH operation.
The difference is that PUT is Destructive and replaces the entire row.
Given that, I think this now is a matter of renaming the method to update
The Airtable API provides two ways in which one can update a record, PATCH (not all fields) and PUT (all fields). I think deciding which type of operation to perform should be decided by the library and made abstract to library users.
I propose making 'patch' and 'put' (offered by the API, but not available in the library yet) private and creating a general 'update' function which decides which of these operation to perform.
This change appears to be feasible and not too time consuming.
The text was updated successfully, but these errors were encountered: