Skip to content

Conversation

@FranAguilera
Copy link
Contributor

@FranAguilera FranAguilera commented Oct 31, 2025

Related to BIT-6764

@FranAguilera FranAguilera changed the title Add breakdown fro JavaScript error type Add breakdown for JavaScript error type Oct 31, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR refines the JavaScript error reporting by splitting the generic JavaScriptError type into two distinct categories: JavaScriptNonFatalError and JavaScriptFatalError, enabling more granular error classification and handling.

Key Changes:

  • Replaced the single JavaScriptError enum value with two specific error types to distinguish between fatal and non-fatal JavaScript errors

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Fran Aguilera <fran@bitdrift.io>
@FranAguilera FranAguilera merged commit 1b6625d into main Oct 31, 2025
2 checks passed
@FranAguilera FranAguilera deleted the franjam/update-non-fatal branch October 31, 2025 10:55
@github-actions github-actions bot locked and limited conversation to collaborators Oct 31, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants