[WEB-2674] chore: open parent issues in peek-overview from the parent badge.

[prateekshourya29]

Issue link: WEB-2674

Summary by CodeRabbit

• New Features

  • Introduced a new navigation component, ControlLink, for improved redirection to parent issue details.
  • Added mobile platform handling for better user experience.

• Bug Fixes

  • Enhanced navigation logic to ensure smooth transitions between issue details.

• Documentation

  • Updated import statements to reflect new components and hooks used in the IssueParentDetail component.

[coderabbitai]

Walkthrough

The pull request introduces modifications to the IssueParentDetail component located in web/core/components/issues/issue-detail/parent/root.tsx. It replaces the Link component from next/link with a new ControlLink component from @plane/ui, which manages navigation to the parent issue's detail page. Additionally, an onClick handler is added to invoke handleRedirection, utilizing new imports for enhanced redirection and platform-specific behavior, while the overall structure of the component remains unchanged.

Changes

File Path	Change Summary
web/core/components/issues/issue-detail/parent/root.tsx	- Replaced Link with ControlLink for navigation. - Added handleRedirection method. - Updated import statements for ControlLink, useIssuePeekOverviewRedirection, and usePlatformOS. - Utilized new hooks for redirection and platform handling.

Possibly related PRs

• [WEB-2613] chore: open parent and sibling issue in new tab from peek-overview/ issue detail page. #5819: Modifications to the IssueParentDetail component that relate to navigation and rendering similar to this PR.
• [WEB-2306] chore: IssueParentDetail added to issue peekoverview #5751: Adds the IssueParentDetail component to PeekOverviewIssueDetails, relevant to the enhancements made in the main PR.
• [WEB-1967] chore: issue load more button improvement #5174: Focuses on styling changes related to the overall issue layout, connecting with navigation and presentation aspects.
• [WEB-2228] fix: dashboard peek overview issue fetch #5442: Includes changes to the IssuePeekOverview component, which may interact with the modified IssueParentDetail.
• [WEB-2308] fix: description editor loader on issue modal when editing sub issue from another project. #5625: Modifies the CreateUpdateIssueModalBase, potentially interacting with the IssueParentDetail in issue management.

Suggested labels

🌐frontend, 🧹chore

Suggested reviewers

• sriramveeraghanta
• SatishGandham

Poem

🐇 In the code where bunnies hop,
A ControlLink now takes the top!
With handleRedirection in play,
Navigating issues in a new way.
Hooray for changes, let’s all cheer,
For hopping forward, the path is clear! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between dd2a05c and 36d92ba.

📒 Files selected for processing (1)

• web/core/components/issues/issue-detail/parent/root.tsx (4 hunks)

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

• web/core/components/issues/issue-detail/parent/root.tsx

---

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 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: 0

🧹 Outside diff range and nitpick comments (1)

web/core/components/issues/issue-detail/parent/root.tsx (1)

48-52: LGTM: ControlLink implementation looks good.

The replacement of Link with ControlLink and the addition of the onClick handler successfully implement the desired functionality for opening parent issues in peek-overview. This change aligns perfectly with the PR objectives.

Consider extracting the onClick handler to a separate function within the component for better readability:

const handleParentIssueClick = () => handleRedirection(workspaceSlug, parentIssue, isMobile);

// Then in JSX:
<ControlLink
  href={`/${workspaceSlug}/projects/${parentIssue?.project_id}/issues/${parentIssue.id}`}
  target="_blank"
  onClick={handleParentIssueClick}
>
  {/* ... */}
</ControlLink>

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between db91942 and dd2a05c.

📒 Files selected for processing (1)

• web/core/components/issues/issue-detail/parent/root.tsx (4 hunks)

🧰 Additional context used

🔇 Additional comments (3)

web/core/components/issues/issue-detail/parent/root.tsx (3)

9-9: LGTM: New imports align with PR objectives.

The addition of ControlLink and new hooks (useIssuePeekOverviewRedirection, usePlatformOS) are consistent with the PR's goal of opening parent issues in peek-overview. These imports set the foundation for the subsequent changes in the component.

Also applies to: 12-13

---

33-34: LGTM: New hooks enhance component functionality.

The addition of handleRedirection from useIssuePeekOverviewRedirection and isMobile from usePlatformOS enhances the component's ability to handle navigation and adapt to different platforms. This is in line with the PR's objective of improving parent issue navigation.

---

Line range hint 1-85: LGTM: Overall implementation is solid.

The changes have been well-integrated into the existing component structure. The core logic for rendering issue details has been preserved, and the new functionality for handling parent issue navigation has been seamlessly added. The implementation maintains a good balance between the existing functionality and the new features.

[SatishGandham]

We don't need target="_blank" on control link.