Skip to content

fix(card): [card] Style pollution caused by modifying the card component #2910

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

Merged
merged 2 commits into from
Feb 18, 2025

Conversation

Youyou-smiles
Copy link
Collaborator

@Youyou-smiles Youyou-smiles commented Feb 17, 2025

card组件index.less文件中修改了input的样式,这里会导致在card组件中使用TinyInput组件input失去边框,因此需要修改。
修改思路是删除index.less文件中的修改input的样式,在相关使用的demo文件中通过穿透的样式去修改input的样式。

Summary by CodeRabbit

  • Style
    • Enhanced card component styling for a more consistent and refined visual presentation.
    • Adjusted the appearance of input elements to ensure a cleaner interface.
    • Streamlined the theme by removing redundant styling for input elements.

@Youyou-smiles Youyou-smiles added the bug Something isn't working label Feb 17, 2025
Copy link

coderabbitai bot commented Feb 17, 2025

Walkthrough

This pull request refines the styling of card-related Vue components and their theme. It updates CSS selectors to use deep selectors for better style penetration, adds new style rules for input elements, and removes an unused input prefix variable and its associated styles from a LESS file. No public API changes were made.

Changes

File(s) Change Summary
examples/sites/demos/pc/app/card/card-select-composition-api.vue
examples/sites/demos/pc/app/card/card-select.vue
Updated deep CSS selectors for .tiny-card--small-padding and introduced new deep style rules for .tiny-input__inner to adjust input appearance within card components.
packages/theme/src/card/index.less Removed the @input-prefix-cls variable and its related class styles, eliminating input-specific styling from the card theme.

Possibly related PRs

Suggested reviewers

  • zzcr

Poem

I'm a rabbit with a style so keen,
Hopping through code in a CSS scene.
Deep selectors guide my every bound,
Making card inputs smooth and sound.
With LESS left lean and changes bright,
I celebrate these tweaks with pure delight!
🐇✨

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.

examples/sites/demos/pc/app/card/card-select-composition-api.vue

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

examples/sites/demos/pc/app/card/card-select.vue

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.


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

Walkthrough

This pull request addresses a style pollution issue in the card component by removing unwanted CSS styles affecting the input elements. The changes involve deleting specific styles from the index.less file and applying necessary styles through scoped styles in demo files.

Changes

Files Summary
examples/sites/demos/pc/app/card/card-select-composition-api.vue, examples/sites/demos/pc/app/card/card-select.vue Updated to use scoped styles with :deep selector for .tiny-card--small-padding and .tiny-input__inner to avoid style pollution.
packages/theme/src/card/index.less Removed global input styles that were causing style pollution in the card component.

Copy link

@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 (2)
examples/sites/demos/pc/app/card/card-select-composition-api.vue (1)

165-169: Consider accessibility implications of input styling.

While the styling fixes the border issue, setting background-color: #fafafa on inputs might affect contrast ratio and accessibility. Consider:

  1. Adding a subtle border or box-shadow for better visual distinction
  2. Ensuring sufficient contrast between input text and background
.card-wrap :deep(.tiny-input__inner) {
  border: none;
  border-radius: 6px;
  background-color: #fafafa;
+ box-shadow: inset 0 0 0 1px rgba(0, 0, 0, 0.1);
}
examples/sites/demos/pc/app/card/card-select.vue (1)

172-179: Consider extracting duplicated styles to a shared file.

These styles are identical to those in card-select-composition-api.vue. To improve maintainability and reduce duplication, consider:

  1. Moving these styles to a shared CSS file
  2. Importing the shared styles in both components

Example approach:

/* shared/card-select-styles.css */
#smb-card :deep(.tiny-card--small-padding) {
  padding: 0;
}

.card-wrap :deep(.tiny-input__inner) {
  border: none;
  border-radius: 6px;
  background-color: #fafafa;
  box-shadow: inset 0 0 0 1px rgba(0, 0, 0, 0.1);
}

Then in both components:

<style scoped>
@import '../shared/card-select-styles.css';
/* component-specific styles... */
</style>
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b2215cb and 5edeb58.

📒 Files selected for processing (3)
  • examples/sites/demos/pc/app/card/card-select-composition-api.vue (1 hunks)
  • examples/sites/demos/pc/app/card/card-select.vue (1 hunks)
  • packages/theme/src/card/index.less (0 hunks)
💤 Files with no reviewable changes (1)
  • packages/theme/src/card/index.less
🔇 Additional comments (1)
examples/sites/demos/pc/app/card/card-select-composition-api.vue (1)

162-164: LGTM! Improved style scoping with :deep selector.

The use of :deep selector helps prevent style pollution by properly scoping the padding styles to the card component.

@zzcr zzcr merged commit 2fefadd into opentiny:dev Feb 18, 2025
3 of 5 checks passed
@Youyou-smiles Youyou-smiles deleted the lty/fix-card branch February 21, 2025 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants