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: fix footer slot content overlapping table in Page component #5518

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

frontendley
Copy link

@frontendley frontendley commented Feb 12, 2025

Description

related to the issue #5494
image

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

  • [√] If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
  • [√] Run the tests with pnpm test.
  • [√] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
  • [√] My code follows the style guidelines of this project
  • [√] I have performed a self-review of my own 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
  • [√] I have added tests that prove my fix is effective or that my feature works
  • [√] New and existing unit tests pass locally with my changes
  • [√] Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

  • Style
    • Refined the footer layout, enhancing its visual appearance and spacing for better on-page positioning.

Copy link

changeset-bot bot commented Feb 12, 2025

⚠️ No Changeset found

Latest commit: 0f2b1f5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Feb 12, 2025

Walkthrough

The change updates the page.vue component by modifying the class binding for the footer <div> element. Specifically, the classes absolute bottom-0 left-0 right-0 have been removed from the binding. The footer now solely uses the classes bg-card align-center flex px-6 py-4, combined with any classes provided via footerClass. No public or exported entity declarations were altered during this update.

Changes

File Change Summary
packages/.../page.vue Removed absolute bottom-0 left-0 right-0 classes from footer <div>; simplified class binding.

Suggested labels

bug

Suggested reviewers

  • anncwb
  • vince292007

Poem

I'm just a rabbit, hopping through the code,
Noticing changes where the footer once strode.
Those pesky classes took their leave today,
Now the layout dances in a cleaner way.
With whiskers twitching and a carrot in hand,
I cheer for clarity across the land!
🐰🥕 Happy coding in this updated land!

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.

packages/effects/common-ui/src/components/page/page.vue

Oops! Something went wrong! :(

ESLint: 9.19.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/node_modules/@vben/eslint-config/dist/index.mjs' imported from /eslint.config.mjs
at finalizeResolution (node:internal/modules/esm/resolve:257:11)
at moduleResolve (node:internal/modules/esm/resolve:914:10)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)


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.

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 (3)
packages/effects/common-ui/src/components/page/page.vue (3)

17-19: Consider using footer height in content calculations to prevent overlap.

While the component tracks both header and footer heights, the footer height (footerHeight) is not used in the content height calculations. This could contribute to overlap issues when the footer is present.

Consider updating the content height calculation to account for the footer:

 const contentStyle = computed<StyleValue>(() => {
   if (autoContentHeight) {
     return {
-      height: `calc(var(${CSS_VARIABLE_LAYOUT_CONTENT_HEIGHT}) - ${headerHeight.value}px)`,
+      height: `calc(var(${CSS_VARIABLE_LAYOUT_CONTENT_HEIGHT}) - ${headerHeight.value}px - ${footerHeight.value}px)`,
       overflowY: shouldAutoHeight.value ? 'auto' : 'unset',
     };
   }
   return {};
 });

Also applies to: 34-44


92-98: LGTM! The removal of absolute positioning should fix the overlap.

The removal of absolute bottom-0 left-0 right-0 classes is the correct approach to fix the footer overlap issue, as it keeps the footer in the normal document flow.

Consider adding a wrapper div with relative class around the footer to maintain proper stacking context if needed:

+    <div class="relative">
       <div
         v-if="$slots.footer"
         ref="footerRef"
         :class="cn('bg-card align-center flex px-6 py-4', footerClass)"
       >
         <slot name="footer"></slot>
       </div>
+    </div>

51-52: Consider adding flex layout for better content distribution.

The component structure is good, but using flex layout could provide better control over content distribution and prevent overlap issues.

Consider updating the root container to use flex layout:

-  <div class="relative">
+  <div class="relative flex min-h-full flex-col">
     <!-- header -->
-    <div :class="cn('h-full p-4', contentClass)" :style="contentStyle">
+    <div :class="cn('flex-1 p-4', contentClass)" :style="contentStyle">
       <slot></slot>
     </div>
     <!-- footer -->
   </div>

Also applies to: 88-90

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e7b0097 and 0f2b1f5.

📒 Files selected for processing (1)
  • packages/effects/common-ui/src/components/page/page.vue (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: post-update (windows-latest)
  • GitHub Check: post-update (ubuntu-latest)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant