-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transfer data integration #13
Conversation
} | ||
}) | ||
.catch((error) => { | ||
console.log(error); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Debugging errors will be challenging since Sentry won't capture these errors, and you'll only find them only in Docker logs. To mitigate this, consider configuring axios validateStatus
(as explained here: link) and consistently return AxiosResponse
instead of AxiosResponse|null
from this function. This way, if an error occurs, Sentry will capture it along with supplementary information such as the transferReportDto
values and you won't need to deal with null
case.
}) | ||
@Post('/reports/transfer') | ||
async transferReport( | ||
@Body() transferReportDto: TransferReportDto, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it necessary to pass the entire TransferReportDto
, or would just the ReportID
suffice for this method?
New endpoint to handle the transfer of a report. Once the transfer is complete the report gets updated with history edits and new external system fields.