feat(UI):Comment box binding issue/pr interface joint debugging

[Ceron-CSS]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
mega	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 1, 2025 3:43am

[Copilot]

Pull Request Overview

This PR implements a unified issue and merge request suggestion system in the comment editor, allowing users to link both issues and PRs with proper type differentiation and enhanced UI functionality.

Key changes:

• Added suggestionType attribute to the LinkIssue extension to distinguish between issues and merge requests
• Created a new hook useGetIssueIssueSuggester for fetching issue/PR suggestions from the API
• Enhanced the suggestion UI with better sizing, custom empty states, and type-specific icons

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
LinkIssue.ts	Added suggestionType attribute to support issue/PR differentiation
useGetIssueIssueSuggester.ts	New hook for fetching issue/PR suggestions via API
SuggestionList.tsx	Added disableEmptyState prop to allow custom empty state handling
LinkIssue.tsx	Enhanced renderer to handle different URL patterns based on suggestion type
SlashCommand.tsx	Added new slash command for linking issues/PRs with $ trigger
MentionList.tsx	Replaced hardcoded data with real API integration and improved UI layout

Comments suppressed due to low confidence (1)

moon/apps/web/components/MarkdownEditor/MentionList.tsx:143

• [nitpick] The variable name suggestionType is ambiguous in this context. Consider renaming it to linkType or entityType to better reflect that it represents the type of entity being linked.

  let suggestionType = ''