fix: improve layout boundary processing

[anncwb]

Description

fixed #4422

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

• If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
• Run the tests with pnpm test.
• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

Release Notes

• New Features

  • Enhanced documentation site with new group icons for improved visual representation.

• Bug Fixes

  • Continuous integration jobs will now run regardless of commit actor or message, ensuring more comprehensive testing and linting.

• Documentation

  • Minor formatting updates in quick-start guide for consistency.

• Chores

  • Updated various dependencies to their latest versions for improved performance and functionality.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7ddd1e0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The pull request includes several changes across multiple files, primarily focusing on modifications to CI workflow conditions, enhancements to VitePress documentation capabilities, updates to package dependencies, and a minor adjustment in a Vue component. The CI jobs are now set to run without restrictions based on the actor or commit message, while new plugins and CSS imports have been added to improve documentation aesthetics. Additionally, some dependencies have been updated to their latest versions for maintenance purposes.

Changes

Files	Change Summary
.github/workflows/ci.yml	Removed conditions for test, lint, and ci-ok jobs to always run, regardless of actor or message.
docs/.vitepress/config/shared.mts	Added vitepress-plugin-group-icons with groupIconMdPlugin and groupIconVitePlugin.
docs/.vitepress/theme/index.ts	Added import for group-icons.css.
docs/package.json	Added dependency for vitepress-plugin-group-icons.
docs/src/guide/introduction/quick-start.md	Changed code block language identifier from bash to sh.
internal/lint-configs/eslint-config/package.json	Updated eslint-plugin-n from ^17.10.2 to ^17.10.3.
internal/tailwind-config/package.json	Updated @iconify/json from ^2.2.249 to ^2.2.250.
internal/vite-config/package.json	Updated @vitejs/plugin-vue from ^5.1.3 to ^5.1.4 and sass from ^1.78.0 to ^1.79.1.
package.json	Updated @vitejs/plugin-vue from ^5.1.3 to ^5.1.4 and cspell from ^8.14.3 to ^8.14.4.
packages/@core/ui-kit/layout-ui/src/components/layout-sidebar.vue	Modified handleMouseenter to accept MouseEvent and added early return condition.

Assessment against linked issues

Objective	Addressed	Explanation
Bug: 当侧边栏未固定时，内容最大化，左侧悬浮会有空白 (#4422)	❌	No changes related to fixing the sidebar bug were made.

Suggested reviewers

• vince292007
• anncwb

Poem

In the garden of code, changes bloom bright,
CI flows freely, no more to fight.
With icons now grouped, our docs shine anew,
A rabbit hops joyfully, sharing the view! 🐇✨
Dependencies updated, all tidy and neat,
Let’s celebrate progress, a wonderful feat!

---

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 generate interesting stats about this repository and render them as a table.
  -- @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.

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (1)

packages/@core/ui-kit/layout-ui/src/components/layout-sidebar.vue (1)

212-216: Approve with a minor suggestion: Consider making the left edge threshold configurable.

The changes to the handleMouseenter function look good! The early return condition effectively prevents unintended behavior when the mouse enters the sidebar from the left edge (within 10 pixels).

As a minor suggestion, consider making the left edge threshold (currently hardcoded as 10) a configurable property or a named constant. This would improve readability and provide flexibility to adjust the threshold if needed.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 26d43ef and 7ddd1e0.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (10)

• .github/workflows/ci.yml (0 hunks)
• docs/.vitepress/config/shared.mts (3 hunks)
• docs/.vitepress/theme/index.ts (1 hunks)
• docs/package.json (1 hunks)
• docs/src/guide/introduction/quick-start.md (1 hunks)
• internal/lint-configs/eslint-config/package.json (1 hunks)
• internal/tailwind-config/package.json (1 hunks)
• internal/vite-config/package.json (1 hunks)
• package.json (1 hunks)
• packages/@core/ui-kit/layout-ui/src/components/layout-sidebar.vue (1 hunks)

Files not reviewed due to no reviewable changes (1)

• .github/workflows/ci.yml

Files skipped from review due to trivial changes (6)

• docs/.vitepress/theme/index.ts
• docs/src/guide/introduction/quick-start.md
• internal/lint-configs/eslint-config/package.json
• internal/tailwind-config/package.json
• internal/vite-config/package.json
• package.json

Additional comments not posted (3)

docs/package.json (1)

17-17: Verify the compatibility and necessity of the new dependency.

The addition of the vitepress-plugin-group-icons dependency seems to align with the project's requirements. However, please ensure that:

• The new dependency is compatible with the existing project setup and dependencies.
• The purpose and functionality provided by this plugin are necessary and beneficial for the project.

docs/.vitepress/config/shared.mts (2)

14-17: LGTM!

The imports of groupIconMdPlugin and groupIconVitePlugin from the vitepress-plugin-group-icons package are valid and follow the correct syntax. These plugins will likely enhance the functionality of the documentation site by enabling the use of group icons.

---

28-28: Looks good!

The usage of groupIconMdPlugin within the markdown pre-configuration section and the addition of groupIconVitePlugin to the Vite plugins array are correct and align with the purpose mentioned in the PR summary and objectives. These changes will enhance the documentation site's functionality by enabling the use of group icons.

Also applies to: 87-87