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

(apps-web)[fix]: Center Dashboard Data on Toggle FullWidth Mode #3371

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

Cedric921
Copy link
Contributor

@Cedric921 Cedric921 commented Nov 26, 2024

Description

Fix #3370

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

Screen.Recording.2024-11-26.at.7.07.28.AM.mov

Current screenshots

Screen.Recording.2024-11-26.at.07.58.36.mov

Summary by CodeRabbit

  • New Features

    • Enhanced layout of the MainPage component for team members by introducing a structured Container for improved organization.
  • Bug Fixes

    • Adjusted local storage retrieval for full-width mode to ensure proper layout rendering.

@Cedric921 Cedric921 added this to the v0.2.0 milestone Nov 26, 2024
@Cedric921 Cedric921 self-assigned this Nov 26, 2024
Copy link
Contributor

coderabbitai bot commented Nov 26, 2024

Walkthrough

The changes in this pull request primarily involve modifications to the MainPage component located in apps/web/app/[locale]/page-component.tsx. The updates include the addition of a Container component for improved layout when displaying the TeamMembers component, particularly for team members. Adjustments to useEffect hooks ensure proper retrieval of layout settings from local storage. The overall structure of the component remains largely unchanged, maintaining its existing functionality while enhancing the layout organization.

Changes

File Path Change Summary
apps/web/app/[locale]/page-component.tsx - Added import for Container from lib/components.
- Wrapped TeamMembers in Container for structured layout.
- Adjusted useEffect hooks for fullWidth state management.

Possibly related PRs

Suggested labels

UI/UX

Suggested reviewers

  • evereq
  • EverTechDevOps

🐇 In the meadow, changes bloom,
A Container wraps, dispelling gloom.
Team members gather, side by side,
With a full-width view, we take pride!
Layouts dance, like rabbits in play,
Enhancing the page, in a joyful way! 🌼

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.

warning @next/eslint-plugin-next > [email protected]: Glob versions prior to v9 are no longer supported
warning @next/eslint-plugin-next > glob > [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning eslint > @humanwhocodes/[email protected]: Use @eslint/config-array instead
warning eslint > @humanwhocodes/config-array > @humanwhocodes/[email protected]: Use @eslint/object-schema instead
warning eslint > file-entry-cache > flat-cache > [email protected]: Rimraf versions prior to v4 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > [email protected]: Glob versions prior to v9 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > glob > [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning prettier-eslint-cli > [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning prettier-eslint-cli > eslint > @humanwhocodes/[email protected]: Use @eslint/config-array instead
warning prettier-eslint-cli > eslint > @humanwhocodes/config-array > @humanwhocodes/[email protected]: Use @eslint/object-schema instead
warning prettier-eslint-cli > @prettier/eslint > [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning @nx/next > @nx/js > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
warning @nx/next > @nx/workspace > nx > [email protected]: Glob versions prior to v9 are no longer supported
warning @nx/next > @nx/workspace > nx > glob > [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning workspace-aggregator-a51435b2-d8ab-4c02-a75f-33d4d8f9a00c > [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning "@nx/eslint-plugin-nx > @nx/[email protected]" has unmet peer dependency "nx@>= 14.1 <= 16".
warning " > [email protected]" has unmet peer dependency "@types/node@".
warning "@nx/next > @nx/[email protected]" has unmet peer dependency "nx@>= 15 <= 17".
warning "@nx/next > [email protected]" has unmet peer dependency "webpack@^4.0.0 || ^5.0.0".
warning "@nx/next > [email protected]" has unmet peer dependency "webpack@^5.1.0".
warning "@nx/next > @babel/[email protected]" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@nx/next > @nx/js > [email protected]" has unmet peer dependency "@types/node@
".
warning "@nx/next > @nx/react > [email protected]" has unmet peer dependency "webpack@^4.0.0 || ^5.0.0".
warning "@nx/next > @babel/plugin-proposal-decorators > @babel/[email protected]" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@nx/next > @babel/plugin-proposal-decorators > @babel/[email protected]" has unmet peer dependency "@babel/core@^7.0.0".
warning "@nx/next > @babel/plugin-proposal-decorators > @babel/helper-create-class-features-plugin > @babel/[email protected]" has unmet peer dependency "@babel/core@^7.0.0".


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.

@Cedric921 Cedric921 linked an issue Nov 26, 2024 that may be closed by this pull request
@Cedric921 Cedric921 marked this pull request as ready for review November 26, 2024 06:07
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]/page-component.tsx (2)

Line range hint 64-67: Optimize fullWidth state initialization

The current implementation can be improved for better reliability and efficiency.

Consider this improved implementation:

  React.useEffect(() => {
-   window && window?.localStorage.getItem('conf-fullWidth-mode');
-   setFullWidth(JSON.parse(window?.localStorage.getItem('conf-fullWidth-mode') || 'true'));
+   try {
+     const stored = localStorage.getItem('conf-fullWidth-mode');
+     setFullWidth(stored ? JSON.parse(stored) : true);
+   } catch (error) {
+     console.error('Error loading fullWidth mode:', error);
+     setFullWidth(true);
+   }
  }, [setFullWidth]);

101-105: Fix indentation in conditional rendering

The JSX indentation is inconsistent, making the code harder to read.

Consider this formatting:

-					<div className="h-full ">{isTeamMember ?
-						<Container fullWidth={fullWidth} className='mx-auto' >
-							<TeamMembers kanbanView={view} />
-						</Container>
-						: <NoTeam />}</div>
+					<div className="h-full">
+						{isTeamMember ? (
+							<Container fullWidth={fullWidth} className="mx-auto">
+								<TeamMembers kanbanView={view} />
+							</Container>
+						) : (
+							<NoTeam />
+						)}
+					</div>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 528362c and 21617c0.

📒 Files selected for processing (1)
  • apps/web/app/[locale]/page-component.tsx (2 hunks)
🔇 Additional comments (2)
apps/web/app/[locale]/page-component.tsx (2)

9-9: LGTM: Clean import addition

The Container import is appropriately grouped with related components.


101-105: LGTM: Proper implementation of centered layout

The Container implementation correctly addresses the centering issue in FullWidth mode:

  • Uses Container component for consistent layout management
  • Properly passes fullWidth state
  • Applies mx-auto for horizontal centering

@evereq evereq merged commit e9de210 into develop Nov 27, 2024
13 checks passed
@evereq evereq deleted the fix/dashboard-fullwidth branch November 27, 2024 17:25
@coderabbitai coderabbitai bot mentioned this pull request Nov 27, 2024
9 tasks
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]: Dashboard | Center Page Data on Toogle FullWidth
2 participants