fix: style optimization

[xuanlid]

English | 简体中文

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)
• Built its own designer, fully self-validated

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:

Background and solution

修改v2.3.0版本样式问题
1.区块设置->事件设置 去掉无必要滚动条显示
2.数据源下拉校验错位

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
  • Updated the list display by removing automatic scrolling for overflow content, leading to a tidier visual presentation.
  • Adjusted the vertical alignment of elements within collection fields, resulting in a refined and more consistent layout appearance.

[coderabbitai]

Walkthrough

This pull request removes specific CSS properties from two Vue components. In the Block component, the overflow: auto; declaration is removed from the .list class, and in the DataSource component, the align-items: center; declaration is removed from the .collection-field-num class. The adjustments affect the scrolling behavior and flex alignment respectively, with no changes to exported or public entities.

Changes

File	Change Summary
packages/.../BlockEventList.vue	Removed overflow: auto; from the .list class in the scoped CSS section.
packages/.../DataSourceFieldCheckRanger.vue	Removed align-items: center; from the .collection-field-num class in the scoped CSS.

Suggested labels

refactor-main

Suggested reviewers

• hexqi
• lichunn

Poem

I'm just a rabbit with a happy hop,
Scrolling no more, styles on top!
CSS changes made, oh what a swing,
CodeRabbit Inc. makes my heart sing.
🐇💻 Keep on coding, let the refactor ring!

---

📜 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 9b3bb55 and 0489be3.

📒 Files selected for processing (2)

• packages/plugins/block/src/BlockEventList.vue (0 hunks)
• packages/plugins/datasource/src/DataSourceFieldCheckRanger.vue (0 hunks)

💤 Files with no reviewable changes (2)

• packages/plugins/datasource/src/DataSourceFieldCheckRanger.vue
• packages/plugins/block/src/BlockEventList.vue

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: push-check

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 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.