Vendor Consents Mapper
The intention of this PR is to avoid calling SetVendorConsentsUseCase with malformed data, if our client (UI) is sending wrong data, we should notify him as soon as possible, allow the malformed data to come in and process only partial changes and without telling nothing to our client, IMO is not a good idea, our client will never know that is sending wrong partialy data so he will never have the opportunity to fix it.
This PR includes:
Add mapper on top of the layers, in the CMP Facade, SetVendorConsentsUseCase will recieve data already mapped and most important, valid, if someone send invalid data, we shouldn't call the use case, immediately we must response with a detailed error.
Vendor Consents Mapper The intention of this PR is to avoid calling SetVendorConsentsUseCase with malformed data, if our client (UI) is sending wrong data, we should notify him as soon as possible, allow the malformed data to come in and process only partial changes and without telling nothing to our client, IMO is not a good idea, our client will never know that is sending wrong partialy data so he will never have the opportunity to fix it.
This PR includes: