fix some detail styles in the plugins

[lichunn]

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

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

Release Notes

• New Features

  • Introduced a full-screen toggle functionality in the MonacoEditor component, enhancing user experience during code editing.
  • Added new checkbox components for filter selection in the BlockGroupFilters component, improving interaction and usability.

• Improvements

  • Streamlined filter selection process with a structured checkbox approach, making it easier for users to manage their selections.
  • Enhanced the visual presentation of various components through CSS adjustments, including margins, paddings, and layout refinements.

• Bug Fixes

  • Resolved layout inconsistencies by removing unnecessary padding and margin properties in multiple components.

• Styling Changes

  • Updated styles across various components for improved visual alignment and user experience.

[coderabbitai[bot]]

Walkthrough

The pull request introduces several enhancements across multiple components, focusing on improving user interaction, visual consistency, and functionality. Key modifications include the addition of new methods and properties for better state management, updates to the template structures for improved accessibility, and styling adjustments to enhance the overall user interface. Components such as MonacoEditor, PluginBlockList, and PageTree received significant updates, including changes to event handling, conditional rendering, and the introduction of new CSS variables for theming.

Changes

File Path	Change Summary
packages/common/component/MonacoEditor.vue	Modified switchFullScreen method to accept a boolean parameter. Updated template for conditional rendering based on fullscreen state. Increased z-index for .editor-container-full and added flex display for .fullscreen.
packages/common/component/PluginBlockList.vue	Updated template and script sections. Added conditional rendering for add blocks. Replaced TinyPopover with TinyTooltip. Adjusted styles for better spacing and visual representation.
packages/toolbars/breadcrumb/src/Main.vue	Introduced a new tiny-button for publishing blocks. Modified open method to set plugins.render based on breadcrumb data. Adjusted styles for the .publish class.
packages/theme/base/src/base.less	Added new CSS variable --te-base-dark-bg-8: rgba(0, 0, 0, 0.16) for theming.
packages/theme/base/src/component-common.less	Significant styling updates across various components for improved visual consistency, including changes to .tiny-select, .tiny-input, .tiny-collapse, .tiny-tree, .tiny-tabs, .tiny-dialog, .tiny-button, and others.
packages/common/component/MetaListItem.vue	Enhanced template readability with line breaks. Updated event bindings for tiny-popover and tiny-dialog-box.
packages/layout/src/ToolbarCollapse.vue	Changed <tiny-popover> trigger from "click" to "hover".
packages/toolbars/save/src/Main.vue	Updated <tiny-popover> trigger from "manual" to "hover". Simplified popover content and removed cancel method.
packages/plugins/bridge/src/BridgeManage.vue	Updated icon name in svg-icon component. Adjusted styles for .list and .list-item classes.
packages/plugins/datasource/src/DataSourceList.vue	Updated svg-button classes and modified styling for .datasource-list-item, .item-label, and .item-handler.
packages/plugins/datasource/src/Main.vue	Added conditional rendering for components based on state. Updated script logic for managing data sources and minor style adjustments.
packages/plugins/i18n/src/Main.vue	Enhanced template layout for i18n functionality. Improved script logic for file uploads and error handling.
packages/plugins/page/src/PageTree.vue	Introduced tiny-search component and updated state management for search functionality. Added new methods for filtering and rendering tree nodes.
packages/theme/light/variable.less	Updated hover color variable from fixed value to reference another variable for dynamic theming.

Suggested labels

enhancement, refactoring

Suggested reviewers

• hexqi

🐰 In a meadow so bright,
Changes hop with delight,
From buttons to styles,
We’ll traverse many miles,
With each tweak and turn,
New lessons we learn! 🌼✨

---

📜 Recent review details

Configuration used: CodeRabbit UI Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between ec05fecd7eee27398fdd37153b378598422842e7 and fc14ce3a4f758ddf069f374d7fbad703cb44365f.

📒 Files selected for processing (1)

• packages/plugins/datasource/src/DataSourceList.vue (3 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• packages/plugins/datasource/src/DataSourceList.vue

---

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