|
my comments on this
1. i believe there should be a dedicated update (patch) service, which fails when a record does not exist
2. in order to limit errors, i believe the UI should use the correct verb for the exposed functionality. for example, if a list of users exposes the ability to edit a user - patch should be used - and not put - so that if an edge case scenario arises where the user is deleted - the update should fail and not re-create the user. this is business use case oriented - but enforcing strictness will limit strange bugs that will most certainly arise along the line
|