Fix: Replace Object.assign with safe Error subclass in error-report r…#833
Merged
RUKAYAT-CODER merged 1 commit intoJun 29, 2026
Merged
Conversation
…oute (rinafcode#714) - Replace Object.assign(new Error(), {...}) with ClientError subclass - Avoids strict mode violations when mutating non-writable Error properties - Ensures instanceof Error checks work correctly on reconstructed objects - PII scrubbing handled by existing logging library redaction
|
@xtrial01 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Thank you for contributing to the project. |
Author
|
thanks for giving the opportunity |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #714 - Replaced Object.assign(new Error(), {...}) with a safe ClientError subclass in the error-report route.
Changes
Acceptance Criteria