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]: Kanban | Cards are broken when Toogle FullWidth Mode #3410

Merged
merged 2 commits into from
Dec 8, 2024

Conversation

Innocent-Akim
Copy link
Contributor

@Innocent-Akim Innocent-Akim commented Dec 8, 2024

Description

Please include a summary of the changes and the related issue.

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 my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings

Previous screenshots

Please add here videos or images of previous status

Current screenshots

Please add here videos or images of previous status

Summary by CodeRabbit

  • New Features
    • Enhanced layout and styling for the Kanban board, improving visual presentation.
  • Bug Fixes
    • Adjusted rendering logic for better clarity and consistency in the Kanban component.
  • Refactor
    • Simplified state management and layout handling within the Kanban components.

Copy link
Contributor

coderabbitai bot commented Dec 8, 2024

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/app/[locale]/kanban/page.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

The pull request introduces modifications to the Kanban and KanbanView components. In page.tsx, a new utility function is imported, and the structure of the component is refined for better readability and layout management. The MainLayout component's children are now conditionally wrapped in a Container. In team-members-kanban-view.tsx, the full-width state management is removed, and layout styles are adjusted. The overall functionality of the Kanban board remains unchanged, with minor refactoring for clarity.

Changes

File Path Change Summary
apps/web/app/[locale]/kanban/page.tsx Added cn utility import, refactored className for tabs, wrapped MainLayout children in Container, adjusted MainLayout closing tag.
apps/web/lib/features/team-members-kanban-view.tsx Removed fullWidthState import and useAtomValue hook, modified ScrollArea className, simplified layout behavior, and refactored rendering logic.

Possibly related PRs

Suggested labels

WEB, Ever Teams

Suggested reviewers

  • evereq
  • Cedric921

Poem

🐰 In the Kanban land where tasks align,
Changes come forth, oh so fine!
With containers wrapped and styles anew,
The board is bright, with a clearer view.
Hopping along, we manage with glee,
A smoother path for you and me! 🌼


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 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: 0

🧹 Outside diff range and nitpick comments (2)
apps/web/app/[locale]/kanban/page.tsx (2)

262-263: Consider maintaining consistent spacing

While empty lines improve readability, consider maintaining a single empty line for consistency with the rest of the codebase.

-
-
+

267-269: Good use of Container component for FullWidth handling

The Container component now properly handles the fullWidth state, which should fix the card display issues. Good use of the cn utility for className management.

Consider extracting the padding values to a constant or theme configuration for better maintainability.

+// Add to a constants file or theme configuration
+const KANBAN_CONTAINER_PADDING = 'px-5';
+
 <Container fullWidth={fullWidth} className={cn("!pt-0 px-5")}>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 88fc30c and ac2b6b9.

📒 Files selected for processing (2)
  • apps/web/app/[locale]/kanban/page.tsx (3 hunks)
  • apps/web/lib/features/team-members-kanban-view.tsx (2 hunks)
🔇 Additional comments (3)
apps/web/lib/features/team-members-kanban-view.tsx (2)

219-251: Code formatting improvements enhance readability

The restructured code maintains the same functionality while being more readable and maintainable.


201-201: Layout improvements look good, but verify edge cases

The increased width (95svw) and consistent height units (svh) should fix the layout issues in FullWidth mode. The reduced padding (px-3) helps maximize space utilization.

Let's verify there are no overflow issues with the new width:

✅ Verification successful

Based on the search results, I can see that the parent components and the overall layout structure properly handle overflow through various CSS classes. Specifically:

  1. The parent layout component (apps/web/lib/layout/main-layout.tsx) has proper overflow handling:
<SidebarInset className="relative flex-1 overflow-x-hidden !h-full !w-full">
...
<div className="!overflow-y-auto custom-scrollbar w-full min-h-svh h-full">
  1. The scrollable container has proper overflow handling with custom scrollbars:
className="!overflow-y-auto custom-scrollbar w-full min-h-svh h-full"
  1. The width increase to 95svw is safely contained within these overflow boundaries.

Layout changes look good with proper overflow handling

The increased width (95svw) is safely contained within parent components that properly handle overflow through overflow-x-hidden and custom scrollbars. The height units (svh) and reduced padding optimize the available space without causing layout issues.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for potential overflow handling in parent components
rg -A 3 "overflow-\w+" 

Length of output: 65996

apps/web/app/[locale]/kanban/page.tsx (1)

165-168: Improved tab styling code organization

The consolidated styling using template literals improves code readability while maintaining the same visual appearance.

@evereq evereq merged commit 34fe05d into develop Dec 8, 2024
13 checks passed
@evereq evereq deleted the fix/kanban-cards-are-broken branch December 8, 2024 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Kanban | Cards are broken when toogle FullWidth Mode
2 participants