[WEB-2612] fix: truncated project name in analytics dropdown

[gakshita]

Summary
This PR fixes the project name overflow in analytics dropddown

[WEB-2612]

Summary by CodeRabbit

• New Features

  • Enhanced the layout of project details in the dropdown options for better readability by constraining the maximum width.

• Bug Fixes

  • Improved the display of project information to prevent overflow and maintain a clean user interface.

[coderabbitai]

Walkthrough

The changes in this pull request involve a modification to the SelectProject component located in the web/core/components/analytics/custom-analytics/select/project.tsx file. The primary update is the addition of a max-w-[300px] class to the div element that wraps project details in the dropdown options. This adjustment constrains the maximum width of the displayed content while preserving the existing layout structure.

Changes

File Path	Change Summary
web/core/components/analytics/custom-analytics/select/project.tsx	Updated SelectProject component to include max-w-[300px] class for the div wrapping project details in dropdown options.

Possibly related PRs

• [WEB-2459] Fix: analytics scroll + dashboard stat minor padding #5613: The changes in the CustomAnalytics component involve layout modifications that may relate to the rendering of dropdowns, similar to the updates made in the SelectProject component regarding the layout of project details in dropdown options.
• [WEB-2512] fix: Large dropdown properties truncation #5672: The changes in the BorderButton and BackgroundButton components to ensure full width may relate to the layout adjustments made in the SelectProject component, which also focuses on the visual presentation of dropdown options.

Suggested labels

🐛bug, 🌐frontend

Suggested reviewers

• SatishGandham
• sriramveeraghanta

🐰 In the dropdown where projects play,
A max width now keeps chaos at bay.
With neat little boxes, all snug and tight,
Our layouts are lovely, a beautiful sight!
So hop along, let’s cheer with delight,
For changes like these make our code feel just right! 🌟

---

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 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

web/core/components/analytics/custom-analytics/select/project.tsx (1)

26-26: LGTM! Consider using a CSS variable for flexibility.

The addition of max-w-[300px] effectively addresses the issue of truncated project names in the analytics dropdown. This change ensures that the dropdown options have a consistent maximum width, improving the overall user experience.

For improved maintainability and flexibility, consider using a CSS variable instead of a hard-coded value. This would allow for easier adjustments across different screen sizes or component instances. Here's a suggested implementation:

1. Define a CSS variable in your global styles:

:root {
  --max-project-width: 300px;
}

2. Update the className to use the CSS variable:

-<div className="flex items-center gap-2 max-w-[300px]">
+<div className="flex items-center gap-2 max-w-[var(--max-project-width)]">

This approach maintains the current functionality while providing more flexibility for future adjustments.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between b745a29 and f9f2ac4.

📒 Files selected for processing (1)

• web/core/components/analytics/custom-analytics/select/project.tsx (1 hunks)

🧰 Additional context used