[WEB-3347] fix: list layout stats indicator

[anmolsinghbhatia]

Description

This PR fixes the placement of the stats indicator in the list layout items.

Type of Change

• Bug fix

References

[WEB-3347]

Summary by CodeRabbit

• Style
  • Adjusted the spacing between elements in the IssueBlock component for improved layout.
  • Modified the width behavior of the issue name display for better visual alignment.

[coderabbitai]

Walkthrough

This pull request involves modifications to the rendering of the IssueBlock component, specifically altering the structure and styling of certain elements. The w-full class has been removed from a paragraph element displaying the issue name, affecting its width behavior. Additionally, a gap-2 class has been added to a parent div, changing the spacing between child elements. No changes were made to the component's logic, state management, or public API declarations.

Changes

File(s)	Change Summary
web/core/.../list/block.tsx	Removed the w-full class from the paragraph element displaying the issue name; added gap-2 class to a parent div for spacing adjustments.

Possibly related PRs

• [WEB-2390] fix: Clickable Area for Issue List Layout Item #5536: The changes in the main PR focus on styling adjustments within the IssueBlock component, while the retrieved PR modifies the structure and interaction model of the same component.
• [WEB-2552] fix: issue list overflow and event propagation #5706: The changes in the main PR are related to the addition of an onClick event handler in the IssueBlock component, which is also modified in the retrieved PR.
• [WEB-2551] fix: list layout item #5704: The changes in the main PR focus on styling adjustments to the IssueBlock component, while the retrieved PR modifies the rendering logic and conditions for displaying elements within the same component.

Suggested reviewers

• sriramveeraghanta
• SatishGandham
• rahulramesha

Poem

I'm a rabbit, hopping through the code,
Skipping away that extra w-full load.
The tooltip now dances with a lighter grace,
Free to shrink and find its own space.
Leaping over bugs with a joyful tune,
Here's to a cleaner code afternoon!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between dab2d81 and 8421b29.

📒 Files selected for processing (1)

• web/core/components/issues/issue-layouts/list/block.tsx (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• web/core/components/issues/issue-layouts/list/block.tsx

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (python)

---

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 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. (Beta)
• @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.