Skip to content

Conversation

@jwang19-atlassian
Copy link
Contributor

@jwang19-atlassian jwang19-atlassian commented Jan 6, 2026

What Is This Change?

Add an error boundary to catch rendering error in Rovo Dev extension, and allow users to see the stack trace and start a new chat session

Doc

https://www.loom.com/share/56cfe258008a4d6b9952b6d69e576ef4

How Has This Been Tested?

Basic checks:

  • npm run lint
  • npm run test

@atlassian
Copy link
Contributor

atlassian bot commented Jan 6, 2026

The issue is ready for review, and the below acceptance criteria have been met:

  • ✅ The ErrorBoundary should catch all rendering errors that would previously break the UI.
  • ✅ Display error logs for users, including stack trace and console logs.

The below acceptance criteria have not been met:

  • ❌ Allow users to easily copy the stack trace to raise a bug to the team.

Check Jira issue

@atlassian
Copy link
Contributor

atlassian bot commented Jan 6, 2026

The issue is ready for review, and the acceptance criteria have been met:

  • ✅ Catch all rendering errors that would previously break the UI.
  • ✅ Display error logs for users, including stack trace and console logs.
  • ✅ Allow users to easily copy the stack trace to raise a bug to the team.

Check Jira issue

sdzh-atlassian
sdzh-atlassian previously approved these changes Jan 6, 2026
Copy link
Member

@sdzh-atlassian sdzh-atlassian left a comment

Choose a reason for hiding this comment

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

Generally LGTM, I'll add a small note in Slack

@jwang19-atlassian jwang19-atlassian merged commit 361e429 into main Jan 8, 2026
13 checks passed
@jwang19-atlassian jwang19-atlassian deleted the axon-1694-error-boundary branch January 8, 2026 00:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants