Skip to content

fix: Fixed the issue of misalignment between the clear and search buttons for four different sizes in mobile first mode of the search component #3378

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

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

Conversation

chenxi-20
Copy link
Collaborator

@chenxi-20 chenxi-20 commented Apr 30, 2025

PR

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our Commit Message Guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • New Features

    • Added an additional search input with a "mini" size option and updated placeholders to reflect input sizes in the demo.
  • Style

    • Standardized button styles for search inputs, ensuring consistent vertical alignment and spacing across all size variants.
  • Refactor

    • Simplified class bindings for search input buttons, reducing complexity and improving maintainability.

@chenxi-20 chenxi-20 added the bug Something isn't working label Apr 30, 2025
Copy link

coderabbitai bot commented Apr 30, 2025

Walkthrough

The updates adjust the search component's appearance and example usage. In the example Vue file, a third search input is added with a new data property, and placeholder texts are standardized to English and aligned with their respective sizes. The search component's internal template simplifies class bindings for anchor elements, removing conditional logic and applying static classes. Corresponding CSS class definitions are consolidated, standardizing button widths and line heights across size variants to ensure uniform styling.

Changes

File(s) Change Summary
examples/sites/demos/mobile-first/app/search/size.vue Added a third <tiny-search> input, new value3 data property, updated placeholders, and adjusted size props.
packages/vue/src/search/src/mobile-first.vue Simplified class bindings on anchor elements by removing conditional logic and using static class assignments.
packages/vue/src/search/src/token.ts Consolidated and standardized CSS class definitions for button anchors, unifying widths and line heights.

Poem

In the garden of code, three searches bloom bright,
With sizes and placeholders, all set just right.
Classes now simpler, the styles unified,
Buttons aligned, no more variants to hide.
A hop and a skip, the UI feels new—
This bunny approves, and so should you! 🐇✨

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/mobile-first/app/search/size.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.

packages/vue/src/search/src/token.ts

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.

packages/vue/src/search/src/mobile-first.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.


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7ca72cd and af3709d.

📒 Files selected for processing (3)
  • examples/sites/demos/mobile-first/app/search/size.vue (2 hunks)
  • packages/vue/src/search/src/mobile-first.vue (2 hunks)
  • packages/vue/src/search/src/token.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: PR E2E Test (pnpm test:e2e3)
🔇 Additional comments (6)
packages/vue/src/search/src/token.ts (2)

44-44: Clean styling fix for clear button alignment

The standardized width (w-8) and consistent line height (leading-none) ensure proper vertical alignment of the clear button across all size variants.


51-51: Clean styling fix for search button alignment

The standardized width (w-11) and consistent line height (leading-none) ensure proper vertical alignment of the search button across all size variants, which directly addresses the misalignment issue mentioned in the PR.

packages/vue/src/search/src/mobile-first.vue (2)

94-94: Simplified class binding for clear button

Good simplification that replaces conditional class bindings with a single static class. This works well with the standardized styling in token.ts and helps maintain consistent button alignment.


114-114: Simplified class binding for search button

Good simplification that replaces conditional class bindings with a single static class. This works well with the standardized styling in token.ts and helps maintain consistent button alignment.

examples/sites/demos/mobile-first/app/search/size.vue (2)

3-5: Improved example with consistent size variants

Good updates to standardize placeholders to match their respective sizes and ensure each component demonstrates the appropriate size variant. This helps verify the fixed alignment works across all size options.


19-20: Added data property for third search component

Appropriate addition of the value3 property to bind to the newly added mini-sized search component.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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

Walkthrough

This PR addresses the misalignment issue between the clear and search buttons in the search component for four different sizes in mobile-first mode. The changes involve modifying the template and styling to ensure proper alignment across different sizes.

Changes

File Summary
examples/sites/demos/mobile-first/app/search/size.vue Updated the template to adjust the placeholders and added a new model for the mini size.
packages/vue/src/search/src/mobile-first.vue Simplified the class binding for clear and search buttons to ensure consistent styling.
packages/vue/src/search/src/token.ts Refined CSS classes to remove size-specific leading properties, ensuring uniform button appearance.

<tiny-search class="demo-search" v-model="value1" size="medium" placeholder="请输入关键词" clearable></tiny-search>
<tiny-search class="demo-search" v-model="value2" size="mini" placeholder="请输入关键词" clearable></tiny-search>
<tiny-search class="demo-search" v-model="value1" size="medium" placeholder="medium" clearable></tiny-search>
<tiny-search class="demo-search" v-model="value2" placeholder="small" clearable></tiny-search>

Choose a reason for hiding this comment

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

Ensure that the placeholder text accurately reflects the intended size for clarity.

"
@click="clear"
>
<a :class="m(gcls('pc-search-input-btn-transtion-a'))" @click="clear">

Choose a reason for hiding this comment

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

The removal of size-specific classes might affect the visual consistency across different sizes. Verify that the new class structure maintains the intended design.

'pc-search-input-btn-transtion-a-medium': 'leading-[calc(theme(spacing.8)-2*theme(borderWidth.DEFAULT))]',
'pc-search-input-btn-transtion-a-mini': 'leading-[calc(theme(spacing.6)-2*theme(borderWidth.DEFAULT))]',
'pc-search-input-btn-transtion-a-unbig': 'leading-[calc(theme(spacing.7)-2*theme(borderWidth.DEFAULT))]',
'pc-search-input-btn-transtion-a': 'no-underline block w-8 leading-none',

Choose a reason for hiding this comment

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

The change to a uniform leading style might impact the button's alignment. Confirm that this change does not introduce new alignment issues.

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.

1 participant