Conversation
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
| const originalMessage = (error as Error)?.message ?? ''; | ||
| const errorMessage = | ||
| originalMessage || messageHandler.parse('FAILED_EXPORT_CONTENT_BRANCH', { branch: targetBranch?.uid }); | ||
| handleAndLogError(error, { ...this.exportConfig.context, branch: targetBranch?.uid }, errorMessage); |
There was a problem hiding this comment.
why we are using both "handleAndLogError" and throw error as well in the same block
There was a problem hiding this comment.
To use both is the old behaviour only, the handleAndLogError does not stop execution, it only logs the error message in accordance with our UI. To stop the execution we need to throw error
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
2 participants
No description provided.