Skip to content

fix: fix form item not align when set display-only #2927

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Feb 20, 2025
Merged

Conversation

gimmyhehe
Copy link
Member

@gimmyhehe gimmyhehe commented Feb 19, 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

  • Style
    • Adjusted spacing and margins for form elements to enhance layout consistency.
    • Refined vertical alignment for labels and input text, improving visual clarity.
    • Improved responsive design settings across mobile components.
    • Updated tooltip styling for a cleaner and more consistent display of preformatted content.

Copy link

coderabbitai bot commented Feb 19, 2025

Walkthrough

This pull request updates the CSS styling for several components. In the theme package, the margin-bottom for the form item is adjusted from mb-5 to mb-4. In the Vue mobile-first components—checkbox, form-item, input, and tooltip—class names have been refined to adjust spacing, padding, and height. The changes modify properties such as leading, min-height, and padding, and update tooltip rendering for preformatted text. No functional or logic changes have been introduced; the adjustments focus solely on visual presentation.

Changes

File(s) Change Summary
packages/theme-saas/.../form-item/index.less Changed margin-bottom by replacing @apply mb-5; with @apply mb-4; in the form item styles.
packages/vue/src/checkbox/src/mobile-first.vue,
packages/vue/src/form-item/src/mobile-first.vue,
packages/vue/src/input/src/mobile-first.vue,
packages/vue/src/tooltip/src/mobile-first.vue
Updated CSS class names for spacing and layout adjustments:
- Checkbox: altered leading value in the label.
- Form-item: refined min-height, padding, and added a new selector for tiny-rate; enhanced label with sm:leading-5.5.
- Input: replaced leading-normal with leading-5.5 and added a pre attribute in the tooltip.
- Tooltip: updated preformatted text styling with a new class.

Possibly related PRs

Suggested labels

bug

Suggested reviewers

  • zzcr

Poem

I'm CodeRabbit, hopping with delight,
Tweaking styles to make our layout just right.
Margins trimmed, and spacing refined,
In theme and Vue, a fresher look aligned.
With joyful hops and a codey cheer,
I celebrate changes that bring clarity near!
🐇💻

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/vue/src/form-item/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.

packages/vue/src/input/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.

packages/vue/src/checkbox/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.

  • 1 others

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.

@github-actions github-actions bot added the bug Something isn't working label Feb 19, 2025
Copy link

Walkthrough

此PR修复了在表单仅展示模式下的对齐问题,主要通过调整样式类的应用来实现。涉及的更改包括对表单项、复选框、输入框和工具提示组件的样式调整。

Changes

文件 概要
packages/theme-saas/src/form-item/index.less 调整表单项的底部边距样式。
packages/vue/src/checkbox/src/mobile-first.vue 修改复选框组件的行高样式。
packages/vue/src/form-item/src/mobile-first.vue 多处样式调整以改善表单项的对齐和显示效果。
packages/vue/src/input/src/mobile-first.vue 调整输入框组件的行高和工具提示的显示样式。
packages/vue/src/tooltip/src/mobile-first.vue 为工具提示的内容添加特定的样式类。

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


Walkthrough

This PR fixes the alignment problem in form display mode, which is mainly achieved by adjusting the application of style classes. Changes involved include style adjustments to form items, check boxes, input boxes, and tooltip components.

Changes

Documents Summary
packages/theme-saas/src/form-item/index.less Adjust the bottom margin style of the form item.
packages/vue/src/checkbox/src/mobile-first.vue Modify the checkbox component's line height style.
packages/vue/src/form-item/src/mobile-first.vue Multiple style adjustments to improve the alignment and display of form items.
packages/vue/src/input/src/mobile-first.vue Adjust the line height of the input box component and the display style of the tooltips.
packages/vue/src/tooltip/src/mobile-first.vue Add specific style classes to the content of the tooltip.

Copy link

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide

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)
packages/vue/src/tooltip/src/mobile-first.vue (1)

117-117: LGTM! Enhanced tooltip text styling.

Added tiny-tooltip-text-pre class for better styling control of pre-formatted text in tooltips.

Consider documenting this class in the component's style guide for future reference.

packages/theme-saas/src/form-item/index.less (1)

19-23: Margin-Bottom Adjustment to Resolve Display-Only Alignment Issues
Changing the default bottom margin from what was likely mb-5 to mb-4 (line 21) should reduce excessive spacing in display-only mode. Please verify that this adjustment achieves the desired alignment across various breakpoints and does not unintentionally impact other form item variants.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4c19d7e and 556983f.

📒 Files selected for processing (5)
  • packages/theme-saas/src/form-item/index.less (1 hunks)
  • packages/vue/src/checkbox/src/mobile-first.vue (1 hunks)
  • packages/vue/src/form-item/src/mobile-first.vue (5 hunks)
  • packages/vue/src/input/src/mobile-first.vue (3 hunks)
  • packages/vue/src/tooltip/src/mobile-first.vue (1 hunks)
🔇 Additional comments (10)
packages/vue/src/checkbox/src/mobile-first.vue (1)

6-6: LGTM! Consistent line height adjustment.

The change from leading-5 to leading-5.5 helps standardize vertical text alignment across form components.

packages/vue/src/form-item/src/mobile-first.vue (3)

6-6: LGTM! Improved form item spacing.

The adjustments to min-height and padding values enhance the form item's layout, particularly in display-only mode.

Also applies to: 15-15


52-52: LGTM! Consistent text alignment.

Added sm:leading-5.5 to standardize vertical text alignment with other form components.


76-77: LGTM! Enhanced responsive layout.

Refined spacing and alignment classes improve the component's behavior across different screen sizes.

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

54-54: LGTM! Standardized text alignment.

Updated to leading-5.5 to maintain consistent vertical text alignment across form components.

Also applies to: 71-71


282-282: LGTM! Enhanced textarea tooltip.

Added pre prop to preserve formatting in textarea tooltips.

packages/theme-saas/src/form-item/index.less (4)

71-74: Refined Line-Height for Medium Form Item Labels
The updated leading-5.5 value in the &--medium &__label selector (line 72) provides finer control over vertical alignment for medium form items. Ensure that this value meshes well with adjacent elements and preserves a consistent vertical rhythm across the UI.


103-106: Adjusted Top Margin on Switch Component
The application of mt-1.5 within the switch component block (line 104) helps tighten its alignment within the form item. Please confirm that this change works harmoniously with both interactive and display-only states.


242-248: Inline Error Spacing Enhancement
The modification to use ml-2.5 for the inline error container (line 247) should help maintain a consistent left margin when error messages are displayed. Ensure that this spacing is compatible with surrounding form elements and does not lead to misalignment issues.


250-257: Validation of Required Field Asterisk Content
The rule using ~"content-['*']" (line 253) for marking required fields is a standard approach. Please test its rendering across target browsers to confirm that the visual indicator appears as intended without causing layout shifts.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants