Skip to content

feat: improve error handling in TraceManager with TraceError class #5603

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

Closed
wants to merge 3 commits into from

Conversation

DeVikingMark
Copy link

Description:

  • Add TraceError class for better error handling and debugging
  • Include step index in error objects for improved context
  • Enhance error messages in buildCallPath, getCallStackAt and getStackAt methods
  • Preserve error context instead of string conversion

Benefits:

  • Better debugging experience with detailed error information
  • Type safety with specialized error class
  • Consistent error handling approach

Copy link

netlify bot commented Jan 6, 2025

👷 Deploy request for remixproject pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 6d35a43

}
throw new TraceError('No stack data found for the given step index', stepIndex)
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this needs to be in a else statement.

Copy link
Author

Choose a reason for hiding this comment

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

@yann300 made an update, and also provided a similar change to another place in code. Does it seem alright to you?

@yann300
Copy link
Contributor

yann300 commented May 14, 2025

Closing that one as we are planning for a refactor.

@yann300 yann300 closed this May 14, 2025
@github-project-automation github-project-automation bot moved this to Closed in Backlog May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Closed
Development

Successfully merging this pull request may close these issues.

3 participants