[BI Data Mapper] Update ErrorBoundary to include correct issue URLs

[KCSAbeywickrama]

Purpose

Resolve wso2/product-ballerina-integrator#2015

Summary by CodeRabbit

• New Features

  • Error screens now include direct links to an external issues URL from the app, making it easier to report problems when errors occur.

• Bug Fixes

  • Updated default issue tracker link to the correct repository so error reports are routed to the appropriate issue platform.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated error-handling configuration by adding issue URL props to ErrorBoundary usages in Data Mapper components and changing the ErrorScreen default issue tracker URL.

Changes

Cohort / File(s)	Summary
Data Mapper ErrorBoundary usages workspaces/ballerina/ballerina-visualizer/src/views/DataMapper/index.tsx, workspaces/ballerina/data-mapper/src/index.tsx	Imported issue URL constants (BALLERINA_INTEGRATOR_ISSUES_URL, ISSUES_URL) and passed them as the issueUrl prop to ErrorBoundary components.
ErrorBoundary default URL workspaces/common-libs/ui-toolkit/src/components/ErrorBoundary/Error/Error.tsx	Changed default issue tracker URL from https://github.com/wso2/ballerina-plugin-vscode/issues to https://github.com/wso2/vscode-extensions/issues.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10–15 minutes

• Check correct import paths and constant names in the two Data Mapper files.
• Verify ErrorBoundary accepts issueUrl and ErrorScreen displays the new default URL correctly.
• Confirm no unintended formatting or lint issues.

Suggested reviewers

• hevayo
• gigara

Poem

🐰 A link, a hop, a tidy trail,
Errors now point where users sail,
Issue URLs set with care,
Bugs can find their way there—hare! ✨

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description only includes the Purpose section with a link to the related issue, but is missing the Goals, Approach, and other required template sections.	Complete the PR description by adding Goals, Approach, and other relevant sections from the template to provide comprehensive context for reviewers.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: updating ErrorBoundary to use correct issue URLs for the Data Mapper.
Linked Issues check	✅ Passed	The PR updates ErrorBoundary to include correct issue URLs in two files (data-mapper and ballerina-visualizer) and changes the default URL, aligning with the objective to update issue tracker URL configuration.
Out of Scope Changes check	✅ Passed	All changes are focused on updating issue URLs in ErrorBoundary components across the relevant modules, with no unrelated modifications detected.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ca02903 and 3463f07.

📒 Files selected for processing (1)

• workspaces/ballerina/data-mapper/src/index.tsx (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• workspaces/ballerina/data-mapper/src/index.tsx

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}