-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WEB-2885] fix: retain issue description when creating an issue copy #6243
Conversation
WalkthroughThe pull request modifies the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
web/core/components/issues/issue-modal/base.tsx (1)
94-96
: Consider adding a comment explaining the sourceIssueId usage.To improve code maintainability, consider adding a comment explaining that
sourceIssueId
is used for retaining the description when copying issues.+ // When copying an issue, fetch description from sourceIssueId if available if (isOpen) fetchIssueDetail(data?.id ?? data?.sourceIssueId);
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
web/core/components/issues/issue-modal/base.tsx
(2 hunks)
🔇 Additional comments (2)
web/core/components/issues/issue-modal/base.tsx (2)
95-95
: LGTM! This change correctly implements issue description retention.
The modification to use both data?.id
and data?.sourceIssueId
ensures that the issue description is properly fetched when creating a copy of an existing issue.
119-119
: Verify the useEffect dependency array update.
The addition of data?.sourceIssueId
to the dependency array is correct and necessary to ensure the effect reruns when copying issues. However, let's verify that this doesn't cause any unintended re-renders in the codebase.
✅ Verification successful
The useEffect dependency array update is correct and safe
The addition of data?.sourceIssueId
to the dependency array is justified based on the codebase analysis:
- It's used within the effect to fetch issue details:
fetchIssueDetail(data?.id ?? data?.sourceIssueId)
sourceIssueId
is only used for copying issues and is properly cleaned up in form submission- The type definition confirms it's a temporary property used only for cloning
- No other components have effects dependent on this property, preventing cascade re-renders
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for potential performance impact of the dependency array change
# Look for other useEffect hooks that might be affected by sourceIssueId changes
rg -U "useEffect.*sourceIssueId.*\}" --type ts --type tsx
# Look for components that might re-render due to sourceIssueId prop changes
ast-grep --pattern 'interface $interface {
$$$
sourceIssueId?: $_
$$$
}'
Length of output: 168
Script:
#!/bin/bash
# Description: Check for potential performance impact of the dependency array change
# Look for other useEffect hooks that might be affected by sourceIssueId changes
rg -U "useEffect.*sourceIssueId.*\}"
# Look for the usage context of sourceIssueId in the component
rg -B 5 -A 5 "sourceIssueId" web/core/components/issues/issue-modal/base.tsx
# Check for other components using sourceIssueId
rg "sourceIssueId" --type typescript --type javascriptreact --type typescriptreact
Length of output: 1615
Script:
#!/bin/bash
# Look for sourceIssueId usage in all files
rg "sourceIssueId"
# Check the component's effect implementation
rg -B 10 -A 10 "useEffect.*fetchIssueDetail" web/core/components/issues/issue-modal/base.tsx
# Look for fetchIssueDetail implementation
rg -B 5 -A 5 "fetchIssueDetail.*=" web/core/components/issues/issue-modal/base.tsx
Length of output: 2542
Description
Ensure the description is included when copying an issue, even if the source issue isn't opened beforehand.
Type of Change
Screenshots and Media
Screen.Recording.2024-12-20.at.1.39.23.PM.mov
References
WEB-2885
Summary by CodeRabbit
New Features
Bug Fixes