Feb 05, 2021 03:57 PM|mgebhard|LINK
Thanks the thing I am trying to think about is having to create a different transport request for the delete endpoint where its 3 of the fields in the same model. Just seems messy to create different request transport objects based on a subset of properties
from the main Get transport model that has all if that makes sense.
I still do not understand the problem or why it is messy. Deleting 3 different resources at once could be as simple as...
Or call three different delete actions.
Ultimately it depends on your business requirements. I have many application where the GET populates an entire page of data from many different sources. The logic within the page might only update a section. I just use a different object than the GET to
do the update.