[WEB-3184]fix: links validations messages

[vamsikrishnamathala]

Description

Updated links messages.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (change that would cause existing functionality to not work as expected)
• Code refactoring
• Performance improvements
• Documentation update

Screenshots and Media (if applicable)

Test Scenarios

References

WEB-3184

Summary by CodeRabbit

• Bug Fixes
  • Improved error handling for link creation and update operations
  • Updated error message retrieval to match new error object structure

[coderabbitai]

Walkthrough

The pull request focuses on modifying error handling logic in the handleLinkOperations function within the helper.tsx file. The key change involves adjusting how error messages are retrieved, specifically updating the path from error?.data?.error to error?.data?.url?.error. This suggests a restructuring of the error object's schema, with error messages now nested under a url property. The update method also includes an explicit type annotation for the error parameter to improve type safety.

Changes

File	Change Summary
web/core/components/issues/issue-detail-widgets/links/helper.tsx	Updated error message retrieval in create and update methods to use error?.data?.url?.error instead of error?.data?.error. Added explicit any type for error parameter in update method's catch block.

Possibly related PRs

• fix: issue and module link validation #5994: Modifications to error handling logic in the same helper.tsx file for link creation and update methods

Suggested reviewers

• rahulramesha
• gurusainath
• sriramveeraghanta

Poem

🐰 A Rabbit's Error Tale 🔍

In the realm of code so bright,
Error paths shifted left and right
From data.error to url.error we leap
Type safety making our logic deep
A small change, a programmer's delight! 🚀

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

web/core/components/issues/issue-detail-widgets/links/helper.tsx (1)

32-32: LGTM! Consider adding type safety.

The error message path update is correct and includes a good fallback message.

Consider defining a type for the expected error structure to improve type safety:

type LinkOperationError = {
  data?: {
    url?: {
      error?: string;
    };
  };
};

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9f4dd77 and 94583d7.

📒 Files selected for processing (1)

• web/core/components/issues/issue-detail-widgets/links/helper.tsx (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (python)