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: long text style in sidemenu. fixed #4749 #4770

Merged
merged 1 commit into from
Oct 30, 2024

Conversation

mynetfan
Copy link
Collaborator

@mynetfan mynetfan commented Oct 30, 2024

Description

修复侧边菜单文字较长时的显示问题

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

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

  • New Features

    • Enhanced menu interactivity and responsiveness, improving handling of dynamic states and resizing.
    • Added new computed properties and methods for better menu item management.
  • Bug Fixes

    • Improved logic for handling menu item interactions and resizing behavior.
  • Style

    • Updated rendering of menu names to enhance output structure.

Copy link

changeset-bot bot commented Oct 30, 2024

⚠️ No Changeset found

Latest commit: ab6d40d

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 Oct 30, 2024

Walkthrough

The changes involve modifications to the menu.vue and sub-menu.vue components in the @core/ui-kit/menu-ui package. The menu.vue component has been enhanced with new computed properties, methods, and improved logic for handling menu interactions and resizing behavior. The sub-menu.vue component has been updated to wrap the menu.name property in a <span> tag for better structure. Overall, these changes aim to improve the functionality and responsiveness of the menu components.

Changes

File Path Change Summary
packages/@core/ui-kit/menu-ui/src/components/menu.vue Added new computed properties and methods, updated existing logic for menu interactions and resizing.
packages/@core/ui-kit/menu-ui/src/sub-menu.vue Wrapped menu.name in a <span> tag for improved structure; no changes to logic or functionality.

Possibly related PRs

Suggested labels

bug

Suggested reviewers

  • vince292007
  • anncwb

Poem

In the menu where we play,
New features hop and sway.
With spans and slices, oh so bright,
Our interactions take to flight!
A rabbit's joy in every click,
Enhancements make the menu slick! 🐇✨


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.

@anncwb anncwb merged commit 353e8be into vbenjs:main Oct 30, 2024
14 checks passed
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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between e600d78 and ab6d40d.

📒 Files selected for processing (2)
  • packages/@core/ui-kit/menu-ui/src/components/menu.vue (1 hunks)
  • packages/@core/ui-kit/menu-ui/src/sub-menu.vue (2 hunks)
🔇 Additional comments (2)
packages/@core/ui-kit/menu-ui/src/sub-menu.vue (1)

45-47: LGTM! Verify styling implementation.

The structural changes to wrap menu names in <span> tags are good. This provides better control for text styling and overflow handling.

Let's verify if the parent components implement the necessary styles for long text:

Also applies to: 64-66

✅ Verification successful

Long text handling is already implemented in menu styles

Found the necessary text overflow handling styles in packages/@core/ui-kit/menu-ui/src/components/menu.vue:

overflow: hidden;
text-overflow: ellipsis;

The wrapping of menu names in <span> tags combined with these existing styles properly handles long text in the menu items. The implementation is complete and correct.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for related style implementations in parent components
rg -t vue 'overflow|text-overflow|whitespace' packages/@core/ui-kit/menu-ui/

Length of output: 106


Script:

#!/bin/bash
# Search for style-related patterns in .vue files
rg -l '\.vue$' packages/@core/ui-kit/menu-ui/ | xargs rg 'overflow|text-overflow|whitespace|ellipsis'

# Also check for any CSS/SCSS files in the menu-ui directory
fd -e css -e scss . packages/@core/ui-kit/menu-ui/ --exec cat {}

Length of output: 15922

packages/@core/ui-kit/menu-ui/src/components/menu.vue (1)

721-724: Fix correctly addresses the long text styling issue in menu items

Wrapping the menu item title with a span and applying the @include menu-title; mixin ensures that long text in the side menu is styled appropriately. This change enhances readability and resolves issue #4749.

Comment on lines +45 to +47
<template #title>
<span>{{ menu.name }}</span>
</template>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Consider adding explicit styles for long text handling.

To ensure consistent handling of long text across all menu items, consider adding specific styles to handle text overflow.

Add styles to the spans:

-      <span>{{ menu.name }}</span>
+      <span class="menu-item-text">{{ menu.name }}</span>

And add these styles in your component:

<style scoped>
.menu-item-text {
  display: block;
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
}
</style>

Also applies to: 64-66

GavinLucky pushed a commit to GavinLucky/vue-vben-admin that referenced this pull request Oct 31, 2024
@mynetfan mynetfan deleted the fix/sidemenu branch November 5, 2024 02:42
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.

2 participants