[Mailman-Developers] REST API PUT versus PATCH - is there in any point in PUT and PATCH?

[Andrew Stuart]

There are several cases in the REST API where there is a PUT method that requires all fields to be present, and also a PATCH method which is the same except that not all fields are required.

Is there any actual benefit in those PUT methods?  I can’t see what they offer over the PATCH methods.

Maybe its worth thinking about removing all PUT methods that don’t offer any substantial gain over the PATCH methods, reducing need for testing, documentation and complexity.

Here are the PUT and PATCH methods in the REST API:

AddressesVARUserPUT
ListsVARArchiversPATCH
ListsVARArchiversPUT
ListsVARConfigPATCH
ListsVARConfigPUT
ListsVARConfigVARPATCH
MembersVARPATCH
MembersVARPreferencesPATCH
MembersVARPreferencesPUT
UsersVARPATCH
UsersVARPUT
UsersVARPreferencesPATCH
UsersVARPreferencesPUT



as