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
Summary
Currently, as shown in the context link, we have some inconsistencies between the current Client Gateway implementation responses and this new service ones. The idea here is, instead of doing ad hoc mapping in the services to the expected formats, having DTOs providing the expected payload format, and implement a serialisation layer which takes "service objects" and converts them to "presentation objects" to fulfil client's requirements.
Note
We could do some additional research here to see what's the best solution, but we're already using AJV to validate incoming payloads so we could use it for serialisation as well.
The text was updated successfully, but these errors were encountered:
Dependencies
Context here.
Summary
Currently, as shown in the context link, we have some inconsistencies between the current Client Gateway implementation responses and this new service ones. The idea here is, instead of doing ad hoc mapping in the services to the expected formats, having DTOs providing the expected payload format, and implement a serialisation layer which takes "service objects" and converts them to "presentation objects" to fulfil client's requirements.
Note
We could do some additional research here to see what's the best solution, but we're already using AJV to validate incoming payloads so we could use it for serialisation as well.
The text was updated successfully, but these errors were encountered: