feat(ui): logo icon support click events

[jinmao88]

在 authentication.vue 中新增 clickLogo 属性，允许在点击 Logo 时执行自定义操作。在 auth.vue 中实现了一个示例的点击事件处理函数，用于测试该功能。

Description

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

• New Features
  • Enhanced the authentication layout with an interactive logo area. Users can now click on the logo and application name, triggering a newly added click event handler that can be customized for further actions.
  • Introduced click event handling in the BasicLayout component, allowing the logo click to emit an event for further interactions.
  • Added a new function to handle logo clicks in the Basic layout, extending its interactivity.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 947f85b

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 changes add an optional clickLogo event handler to the authentication components. In the authentication.vue file, the Props interface is updated to include clickLogo with a default empty function, and the logo area is bound with an @click listener. In the auth.vue file, a new clickLogo method is introduced as an empty function and passed as a prop to the layout component. The BasicLayout component is updated to emit a clickLogo event, enhancing interactivity across components.

Changes

File(s)	Change Summary
packages/effects/…/authentication.vue	Added an optional clickLogo property to the Props interface and a default implementation in withDefaults. Bound the @click event to the logo area.
playground/src/…/auth.vue	Introduced a clickLogo constant as an empty function and passed it as a prop (click-logo) to AuthPageLayout.
packages/effects/…/layout.vue	Updated defineEmits to include clickLogo and added a method to emit this event. Modified the template to call clickLogo on logo click.
playground/src/…/basic.vue	Added handleClickLogo function as an empty function and set up an event listener for @click-logo to call this function.

Suggested reviewers

• mynetfan
• vince292007
• anncwb

Poem

I'm a hopping rabbit, full of cheer,
Code brings a click, oh so dear.
A tiny function makes a logo glow,
With every log, my joy does grow.
Carrots and codes—hip hip, let's go!

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 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 2618148 and 421235e.

📒 Files selected for processing (4)

• packages/effects/layouts/src/authentication/authentication.vue (3 hunks)
• packages/effects/layouts/src/basic/layout.vue (3 hunks)
• playground/src/layouts/auth.vue (2 hunks)
• playground/src/layouts/basic.vue (2 hunks)

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

• playground/src/layouts/auth.vue
• playground/src/layouts/basic.vue
• packages/effects/layouts/src/authentication/authentication.vue
• packages/effects/layouts/src/basic/layout.vue

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

• GitHub Check: post-update (ubuntu-latest)
• GitHub Check: post-update (windows-latest)
• GitHub Check: Check (ubuntu-latest)
• GitHub Check: Check (windows-latest)
• GitHub Check: Lint (ubuntu-latest)
• GitHub Check: Test (windows-latest)
• GitHub Check: Lint (windows-latest)
• GitHub Check: Analyze (javascript-typescript)

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

playground/src/layouts/basic.vue (1)

109-111: Implement a meaningful logo click handler.

While the implementation correctly logs to the console, consider adding a more substantial action for production use, such as navigation to the home page. Console logs should generally be removed in production code.

function handleClickLogo() {
-  console.log('=>(basic.vue:111) handleClickLogo');
+  // Navigate to home or another meaningful action
+  // For example: router.push('/');
}

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b5fe630 and 46491d8.

📒 Files selected for processing (2)

• packages/effects/layouts/src/basic/layout.vue (3 hunks)
• playground/src/layouts/basic.vue (2 hunks)

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

• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Check (windows-latest)
• GitHub Check: Check (ubuntu-latest)
• GitHub Check: Test (windows-latest)
• GitHub Check: Lint (windows-latest)
• GitHub Check: Lint (ubuntu-latest)
• GitHub Check: post-update (windows-latest)
• GitHub Check: post-update (ubuntu-latest)

🔇 Additional comments (4)

playground/src/layouts/basic.vue (1)

131-134: LGTM! Event binding implementation looks good.

The event binding for the click-logo event is properly implemented and aligns with the PR objectives.

packages/effects/layouts/src/basic/layout.vue (3)

37-37: LGTM! Event declaration looks good.

The updated emit declaration correctly includes the new clickLogo event alongside the existing one.

---

152-154: LGTM! Event emission implementation is correct.

The clickLogo function has a single responsibility of emitting the event, following good practices.

---

228-228: LGTM! Logo click event is properly connected.

The click event on the VbenLogo component is correctly bound to the clickLogo function.