Skip to content
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

[FIX]: Buttons Moving Out of Container on Task Detail Page #3577

Merged
merged 2 commits into from
Feb 3, 2025

Conversation

sv7000
Copy link
Contributor

@sv7000 sv7000 commented Feb 3, 2025

Issue No: #3575
closes #3575

Description

The issue where buttons were moving out of their container on the Task Detail page when the sidebar was expanded has been fixed. The buttons now remain properly aligned within their container.

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented on my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings

Previous screenshots

Screenshot 2025-02-03 at 7 39 25 PM

Current screenshots

Screenshot 2025-02-03 at 7 44 37 PM

Summary by CodeRabbit

  • Style
    • Adjusted component widths to improve layout consistency on the task details page.
    • Refined spacing by updating padding on buttons and adding margin to icons for a more polished visual presentation.

@sv7000 sv7000 self-assigned this Feb 3, 2025
Copy link
Contributor

coderabbitai bot commented Feb 3, 2025

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

apps/web/components/pages/task/details-section/blocks/task-secondary-info.tsx

Oops! Something went wrong! :(

ESLint: 8.46.0

ESLint couldn't find the config "next/core-web-vitals" to extend from. Please check that the name of the config is correct.

The config "next/core-web-vitals" was referenced from the config file in "/apps/web/.eslintrc.json".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

Walkthrough

This change adjusts the UI styling of several components within the TaskSecondaryInfo module. The updates modify the class names to update width constraints on multiple dropdown components, adjust the button padding, and replace a max-width style with a min-width style in the TaskLabels component. These changes refine spacing and layout without altering underlying functionality.

Changes

File Summary of Changes
apps/web/.../task-secondary-info.tsx - Updated class names for ActiveTaskVersionDropdown, ActiveTaskStatusDropdown, TaskLabels, ActiveTaskSizesDropdown, and ActiveTaskPropertiesDropdown.
- Changed dropdown minimum width from 170px to 130px.
- Modified TaskLabels' taskStatusClassName property from max-w-[7.6875rem] to min-w-[7.6875rem].
- Adjusted Listbox.Button padding from px-4 to px-2 and added margin for the ProjectIcon wrapper.

Possibly related PRs

Suggested labels

UI/UX, Bug fix

Suggested reviewers

  • evereq
  • Innocent-Akim
  • NdekoCode

Poem

Hi, I'm a little rabbit hopping by,

Noticing tweaks that make the layout fly.

With dropdowns slim and buttons neat,

My code garden is now extra sweet!

Cheers to changes, under moonlit sky!


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

@sv7000 sv7000 requested review from CREDO23 and evereq February 3, 2025 18:21
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: 0

🧹 Nitpick comments (1)
apps/web/components/pages/task/details-section/blocks/task-secondary-info.tsx (1)

89-232: Consider extracting dropdown components for better maintainability.

The TaskSecondaryInfo component contains multiple similar dropdown sections. Consider extracting these into a reusable component to reduce code duplication and improve maintainability.

Example refactor:

interface TaskDropdownProps {
  labelTitle: string;
  component: React.ReactElement;
  wrapperClassName?: string;
}

const TaskDropdownRow: React.FC<TaskDropdownProps> = ({ labelTitle, component, wrapperClassName }) => (
  <TaskRow labelTitle={labelTitle} wrapperClassName={wrapperClassName}>
    {component}
  </TaskRow>
);

Then use it like:

-<TaskRow labelTitle={t('pages.taskDetails.VERSION')}>
-  <ActiveTaskVersionDropdown
-    task={task}
-    className="lg:min-w-[130px] text-black"
-    forDetails={true}
-    sidebarUI={true}
-    taskStatusClassName="text-[0.625rem] w-[7.6875rem] h-[2.35rem] max-w-[7.6875rem] rounded 3xl:text-xs"
-  >
-    <Button
-      className="w-full py-1 px-2 text-[0.625rem] mt-3  dark:text-white dark:border-white"
-      variant="outline"
-      onClick={openModalEditionHandle('version')}
-    >
-      <PlusIcon className="w-4 h-4" />
-    </Button>
-  </ActiveTaskVersionDropdown>
-</TaskRow>
+<TaskDropdownRow
+  labelTitle={t('pages.taskDetails.VERSION')}
+  component={
+    <ActiveTaskVersionDropdown
+      task={task}
+      className="lg:min-w-[130px] text-black"
+      forDetails={true}
+      sidebarUI={true}
+      taskStatusClassName="text-[0.625rem] w-[7.6875rem] h-[2.35rem] max-w-[7.6875rem] rounded 3xl:text-xs"
+    >
+      <Button
+        className="w-full py-1 px-2 text-[0.625rem] mt-3  dark:text-white dark:border-white"
+        variant="outline"
+        onClick={openModalEditionHandle('version')}
+      >
+        <PlusIcon className="w-4 h-4" />
+      </Button>
+    </ActiveTaskVersionDropdown>
+  }
+/>
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e60c210 and a67b773.

📒 Files selected for processing (1)
  • apps/web/components/pages/task/details-section/blocks/task-secondary-info.tsx (6 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: deploy
🔇 Additional comments (4)
apps/web/components/pages/task/details-section/blocks/task-secondary-info.tsx (4)

95-95: LGTM! Width constraints adjusted to prevent overflow.

The change from min-w-[170px] to min-w-[130px] across all dropdown components helps prevent buttons from moving out of their container when the sidebar expands.

Also applies to: 134-134, 153-153, 182-182, 201-201


155-155: LGTM! Fixed width constraint type.

Changed from max-w-[7.6875rem] to min-w-[7.6875rem] to maintain consistent width and prevent content from shrinking below the desired width.


363-363: LGTM! Adjusted button padding.

Reduced horizontal padding from px-4 to px-2 to ensure button content stays within the container bounds.


370-370: LGTM! Added margin for icon alignment.

Added mx-1 margin to the ProjectIcon wrapper to maintain proper spacing within the button.

@evereq evereq merged commit 8bc8682 into develop Feb 3, 2025
13 checks passed
@evereq evereq deleted the Fix/correct-buttons-overflow branch February 3, 2025 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Buttons Moving Out of Container on Task Detail Page
2 participants