Open mit-27 opened 4 weeks ago
For case 2 you're right ! Thats something we must do ! For case 1, actually if im not ingesting its because its not needed but if you've came across a bug where inges must be done and not only unification let me know !
coreUnificationService.unify
method. In contrast, others useingestService.ingestData
.ingestService.ingestData
, which ensures that the nested object will be stored in the database and will return a unified object that will be stored in the main object’s unified format.tcg_comments
).add<object>
method, which calls the respective third party’s method to add the object, we also call third-party endpoints for both the original object and its nested object. Instead of returning the response data of the original object, we assign the nested object’s response data inside the original object’s response data (for example, if we receive comment response data and ticket response data, thenticketResponse.data.comment = commentResponse.data
). After this, the response data is passed to the unify method. Here, as mentioned in Case 1, we check for nested objects and utilize ingestData to store the nested object inside its respective database table.