Skip to content

chore: issue detail refactor #6803

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

Merged
merged 1 commit into from
Mar 24, 2025
Merged

Conversation

vamsikrishnamathala
Copy link
Member

@vamsikrishnamathala vamsikrishnamathala commented Mar 24, 2025

Description

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

Summary by CodeRabbit

  • New Features

    • Integrated an additional widget module into the issue details view, enabling enhanced work item information display.
    • Introduced improved sorting for work items, offering a more intuitive ordering experience.
  • Refactor

    • Streamlined the issue sidebar by removing an outdated view mode, contributing to a cleaner interface.

Copy link
Contributor

coderabbitai bot commented Mar 24, 2025

Walkthrough

This pull request introduces a new React component along with its associated type for additional work item widgets. The new component is integrated into the existing issue detail widgets, and an export has been added to streamline imports. Additionally, a helper function for sorting issue arrays is introduced, and a prop removal update has been made in the issue sidebar component.

Changes

File(s) Change Summary
web/ce/components/issues/issue-detail-widgets/additional-widgets.tsx
web/ce/components/issues/issue-detail-widgets/index.ts
Added a new type TWorkItemAdditionalWidgets and its corresponding functional component WorkItemAdditionalWidgets. The module index has been updated to export these new entities.
web/ce/store/issue/helpers/base-issue-store.ts Added the function workItemSortWithOrderByExtended which processes an array of issues by invoking getIssueIds.
web/core/components/issues/issue-detail-widgets/issue-detail-widget-collapsibles.tsx Integrated the WorkItemAdditionalWidgets component into the collapsibles component by rendering it with appropriate props.
web/core/components/issues/issue-detail/sidebar.tsx Removed the isPeekView prop from the WorkItemAdditionalSidebarProperties component within the sidebar.

Sequence Diagram(s)

sequenceDiagram
    participant Collapsibles as IssueDetailWidgetCollapsibles
    participant AddWidgets as WorkItemAdditionalWidgets

    Collapsibles->>+AddWidgets: Render with props (workspaceSlug, projectId, workItemId, disabled)
    AddWidgets-->>-Collapsibles: Return rendered fragment
Loading
sequenceDiagram
    participant Caller as SortCaller
    participant Store as BaseIssueStore
    participant Utils as BaseIssuesUtils

    Caller->>+Store: workItemSortWithOrderByExtended(issues, key?)
    Store->>+Utils: getIssueIds(issues)
    Utils-->>-Store: sorted IDs
    Store-->>-Caller: Return sorted result
Loading

Possibly related PRs

Suggested labels

🌟improvement

Suggested reviewers

  • prateekshourya29
  • sriramveeraghanta

Poem

In the code garden, I hop with delight,
New widgets bloom, shining ever so bright.
I skip through functions with a joyful tune,
Sorting issues under a code-lit moon.
A bunny's cheer in every line of code—hurray! 🐰✨

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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.
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
web/ce/components/issues/issue-detail-widgets/additional-widgets.tsx (1)

10-10: Empty component implementation.

The component currently renders an empty fragment. While this is likely intentional as part of the refactoring process, make sure to add implementation or documentation comment if this is meant to be extended later.

Consider adding a TODO comment if implementation is planned for the future:

-export const WorkItemAdditionalWidgets: FC<TWorkItemAdditionalWidgets> = (props) => <></>;
+// TODO: Implement additional widgets for work items
+export const WorkItemAdditionalWidgets: FC<TWorkItemAdditionalWidgets> = (props) => <></>;
web/core/components/issues/issue-detail-widgets/issue-detail-widget-collapsibles.tsx (1)

72-78: Consider conditional rendering for consistency.

Unlike other widgets in this component which are conditionally rendered based on certain criteria, the WorkItemAdditionalWidgets component is always rendered. While this may be intentional if the component handles its own visibility, it's inconsistent with the pattern used for other widgets.

Consider wrapping this component in a conditional check for consistency with other widgets, if appropriate:

-      <WorkItemAdditionalWidgets
-        workspaceSlug={workspaceSlug}
-        projectId={projectId}
-        workItemId={issueId}
-        disabled={disabled}
-      />
+      {/* Add appropriate condition here */}
+      {true && (
+        <WorkItemAdditionalWidgets
+          workspaceSlug={workspaceSlug}
+          projectId={projectId}
+          workItemId={issueId}
+          disabled={disabled}
+        />
+      )}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between dbdf2f0 and a740065.

📒 Files selected for processing (5)
  • web/ce/components/issues/issue-detail-widgets/additional-widgets.tsx (1 hunks)
  • web/ce/components/issues/issue-detail-widgets/index.ts (1 hunks)
  • web/ce/store/issue/helpers/base-issue-store.ts (1 hunks)
  • web/core/components/issues/issue-detail-widgets/issue-detail-widget-collapsibles.tsx (2 hunks)
  • web/core/components/issues/issue-detail/sidebar.tsx (0 hunks)
💤 Files with no reviewable changes (1)
  • web/core/components/issues/issue-detail/sidebar.tsx
🧰 Additional context used
🧬 Code Definitions (1)
web/core/components/issues/issue-detail-widgets/issue-detail-widget-collapsibles.tsx (1)
web/ce/components/issues/issue-detail-widgets/additional-widgets.tsx (1)
  • WorkItemAdditionalWidgets (10-10)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: CodeQL
  • GitHub Check: Analyze (javascript)
  • GitHub Check: Analyze (python)
🔇 Additional comments (3)
web/ce/components/issues/issue-detail-widgets/index.ts (1)

1-1: LGTM! Good export pattern.

This export statement follows good module organization practices by re-exporting all entities from the additional-widgets module, making them accessible through a single entry point.

web/ce/components/issues/issue-detail-widgets/additional-widgets.tsx (1)

3-8: LGTM! Clear type definition.

The type definition for TWorkItemAdditionalWidgets is well-structured with appropriate property types.

web/core/components/issues/issue-detail-widgets/issue-detail-widget-collapsibles.tsx (1)

14-14: LGTM! Proper import of the new component.

The import statement correctly brings in the new WorkItemAdditionalWidgets component.

@sriramveeraghanta sriramveeraghanta merged commit e8718a8 into preview Mar 24, 2025
5 of 6 checks passed
@sriramveeraghanta sriramveeraghanta deleted the chore-issues_detail_refactor branch March 24, 2025 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants