Skip to content

[issue-#6952]Cycle Details Sidebar resize #6953

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

Open
wants to merge 1 commit into
base: preview
Choose a base branch
from

Conversation

seifknani
Copy link

@seifknani seifknani commented Apr 21, 2025

Description

This PR works on resizing the Cycle Details sidebar for better visibility of the information.

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)

This is the sidebar minimum width:
Capture d’écran 2025-04-21 182318

This is the sidebar with the maximum width:
Capture d’écran 2025-04-21 182347

Test Scenarios

Resizing the sidebar for a better visibility of the details especially with the progress chart.

References

#6952

Summary by CodeRabbit

  • New Features
    • Introduced a resizable sidebar in the project cycle detail page, allowing users to adjust the sidebar width between 300 and 500 pixels for a more customizable viewing experience.

@CLAassistant
Copy link

CLAassistant commented Apr 21, 2025

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

coderabbitai bot commented Apr 21, 2025

Walkthrough

This update modifies the CycleDetailPage component to introduce a resizable sidebar. It adds state and refs to manage the sidebar's width and resizing state, and implements mouse event handlers to allow users to adjust the sidebar's width by dragging a vertical bar. The sidebar's width is now dynamically controlled within a specified range, replacing the previously fixed-width sidebar. No other business logic or error handling changes are included.

Changes

File(s) Change Summary
web/app/[workspaceSlug]/(projects)/projects/(detail)/[projectId]/cycles/(detail)/[cycleId]/page.tsx Added resizable sidebar: introduced sidebarWidth state, sidebarRef and isResizing refs, mouse handlers, and updated sidebar rendering to support dynamic width.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Sidebar (UI)
    participant CycleDetailPage (Component)
    
    User->>Sidebar (UI): MouseDown on drag bar
    Sidebar (UI)->>CycleDetailPage: handleMouseDown()
    User->>Sidebar (UI): MouseMove (dragging)
    Sidebar (UI)->>CycleDetailPage: Adjust sidebarWidth state
    User->>Sidebar (UI): MouseUp (release)
    Sidebar (UI)->>CycleDetailPage: End resizing, cleanup listeners
Loading

Possibly related issues

Poem

A sidebar once fixed, now slides with delight,
Drag left or right, adjust to your sight.
With code and with care, the width you command,
A rabbit applauds with a hop and a hand.
Resize with a smile—your cycles in style!
🐇🎉

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.
✨ 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 (1)
web/app/[workspaceSlug]/(projects)/projects/(detail)/[projectId]/cycles/(detail)/[cycleId]/page.tsx (1)

53-83: Mouse event handlers for sidebar resizing functionality.

The resize implementation follows good practices by:

  1. Preventing default browser behavior
  2. Disabling text selection during resize
  3. Setting constraints (300-500px range)
  4. Properly cleaning up event listeners

However, there's a minor optimization possible by using a debounce function for the mousemove handler to improve performance during resize operations.

Consider debouncing the mousemove handler to improve performance, especially on slower devices:

+ import { debounce } from 'lodash'; // Add to imports

  const handleMouseDown = (e: React.MouseEvent) => {
    e.preventDefault();
    isResizing.current = true;
    
    document.body.style.userSelect = "none";

    const startX = e.clientX;
    const startWidth = sidebarRef.current?.offsetWidth || sidebarWidth;
  
-   const handleMouseMove = (e: MouseEvent) => {
+   const handleMouseMove = debounce((e: MouseEvent) => {
      if (!isResizing.current) return;
  
      const newWidth = startWidth - (e.clientX - startX);
      if (newWidth >= 300 && newWidth <= 500) {
        setSidebarWidth(newWidth);
      }
-   };
+   }, 10);
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between eac1115 and b48863b.

📒 Files selected for processing (1)
  • web/app/[workspaceSlug]/(projects)/projects/(detail)/[projectId]/cycles/(detail)/[cycleId]/page.tsx (5 hunks)
🔇 Additional comments (3)
web/app/[workspaceSlug]/(projects)/projects/(detail)/[projectId]/cycles/(detail)/[cycleId]/page.tsx (3)

5-5: Added necessary React hooks for sidebar resizing.

The import now correctly includes useRef and useState hooks which are required for implementing the new resizable sidebar functionality.


24-25: State setup for sidebar resizing functionality.

The sidebarWidth state is initialized with 344 pixels which serves as the default width for the sidebar. Good practice to define this as a state variable since it will change dynamically based on user interaction.


43-44: References for tracking sidebar element and resize state.

The two refs are well-designed for their purposes:

  • sidebarRef tracks the sidebar DOM element
  • isResizing is a boolean flag to track whether a resize operation is in progress

Using refs for these purposes is appropriate since they persist between renders without causing re-renders themselves.

Comment on lines +104 to +125
<div
ref={sidebarRef}
className={cn(
"flex h-full flex-shrink-0 flex-col gap-3.5 overflow-y-auto border-l border-custom-border-100 bg-custom-sidebar-background-100 px-4 duration-300 vertical-scrollbar scrollbar-sm absolute right-0 z-[13]"
)}
style={{
width: sidebarWidth,
boxShadow:
"0px 1px 4px 0px rgba(0, 0, 0, 0.06), 0px 2px 4px 0px rgba(16, 24, 40, 0.06), 0px 1px 8px -1px rgba(16, 24, 40, 0.06)",
}}
>
<CycleDetailsSidebar
handleClose={toggleSidebar}
cycleId={cycleId.toString()}
projectId={projectId.toString()}
workspaceSlug={workspaceSlug.toString()}
/>
<div
onMouseDown={handleMouseDown}
className="absolute left-0 top-0 h-full w-2 cursor-col-resize z-[14] transition-colors hover:bg-black/5 active:bg-black/10"
/>
</div>
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Resizable sidebar implementation with drag handle.

The sidebar container has been updated properly to use the dynamic width state with good styling for the resize handle. A few suggestions:

  1. Consider adding ARIA attributes for accessibility
  2. Save the resized width to localStorage for user preference persistence

Enhance the implementation with accessibility and persistence:

<div
  ref={sidebarRef}
  className={cn(
    "flex h-full flex-shrink-0 flex-col gap-3.5 overflow-y-auto border-l border-custom-border-100 bg-custom-sidebar-background-100 px-4 duration-300 vertical-scrollbar scrollbar-sm absolute right-0 z-[13]"
  )}
+ aria-label="Cycle details sidebar"
  style={{
    width: sidebarWidth,
    boxShadow:
      "0px 1px 4px 0px rgba(0, 0, 0, 0.06), 0px 2px 4px 0px rgba(16, 24, 40, 0.06), 0px 1px 8px -1px rgba(16, 24, 40, 0.06)",
  }}
>
  <CycleDetailsSidebar
    handleClose={toggleSidebar}
    cycleId={cycleId.toString()}
    projectId={projectId.toString()}
    workspaceSlug={workspaceSlug.toString()}
  />
  <div
    onMouseDown={handleMouseDown}
+   role="separator"
+   aria-controls="sidebar-content"
+   aria-valuenow={sidebarWidth}
+   aria-valuemin={300}
+   aria-valuemax={500}
    className="absolute left-0 top-0 h-full w-2 cursor-col-resize z-[14] transition-colors hover:bg-black/5 active:bg-black/10"
  />
</div>

Then, update the handleMouseUp function to save the width preference:

const handleMouseUp = () => {
  isResizing.current = false;
  document.body.style.userSelect = "";
+ localStorage.setItem('cycle_sidebar_width', sidebarWidth.toString());
  window.removeEventListener("mousemove", handleMouseMove);
  window.removeEventListener("mouseup", handleMouseUp);
};

And load the saved width at initialization:

- const [sidebarWidth, setSidebarWidth] = useState(344);
+ const [sidebarWidth, setSidebarWidth] = useState(() => {
+   const savedWidth = localStorage.getItem('cycle_sidebar_width');
+   return savedWidth ? parseInt(savedWidth, 10) : 344;
+ });

@sriramveeraghanta
Copy link
Member

Our team is evaluating your changes, We are working on coming up a reusable hook to handle these scenarios across the platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants