[WEB-2482] fix: list layout quick action styling

[anmolsinghbhatia]

Changes:

This PR addresses list layout quick action menu overlapping issue.

Reference:

[WEB-2482]

Summary by CodeRabbit

• New Features

  • Enhanced the list group's header behavior to become sticky when the group is expanded and contains issues, improving visibility and usability.

• Bug Fixes

  • Improved responsiveness of the list group component to user interactions.

[coderabbitai]

Walkthrough

The changes in this pull request focus on the ListGroup component, specifically modifying the class names applied to the Row element. The class names are now conditionally applied based on the isExpanded state and the groupIssueCount. This enhancement allows the Row to become sticky only when certain conditions are met, improving the user interface's responsiveness to user interactions.

Changes

File Path	Change Summary
web/core/components/issues/issue-layouts/list/list-group.tsx	Updated Row class names to be conditional based on isExpanded and groupIssueCount.

Possibly related PRs

• [WEB-2467] fix: platform bug #5621: Involves validation for drag-and-drop functionality in the list layout, relevant to user interactions in the ListGroup component.
• [WEB-2443] fix: project member validation #5601: Modifies role validation logic in project settings, potentially related to conditional rendering in the ListGroup.
• [WEB-2443] fix: project favorite permission validation #5587: Changes in ProjectCard regarding user permission checks, related to UI responsiveness based on user interactions.

Suggested reviewers

• sriramveeraghanta
• SatishGandham
• rahulramesha

Poem

🐇 In the list where issues play,
A sticky header finds its way.
Expanded groups, a sight to see,
With class names dancing joyfully!
So hop along, let’s cheer and sing,
For UI changes that joyfully spring! 🌼

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1c0c158 and 0009b73.

Files selected for processing (1)

• web/core/components/issues/issue-layouts/list/list-group.tsx (1 hunks)

Additional comments not posted (1)

web/core/components/issues/issue-layouts/list/list-group.tsx (1)

236-239: LGTM!

The conditional class names applied to the Row component enhance the user interface by making the header sticky when the group is expanded and contains issues. This improves the usability and navigation within the list group.

---

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 generate interesting stats about this repository and render them as a table.
  -- @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.