fix: the list in ViewerSwitcher does not close after clicking the canvas

[gene9831]

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

• New Features
  • Improved the preview switching experience by ensuring that any open popover automatically closes during transitions, leading to smoother and more responsive interactions.
  • Enhanced event handling capabilities by broadcasting mousedown events from the canvas component.

[coderabbitai]

Walkthrough

The changes modify the canvas viewer components. In the CanvasContainer.vue file, a line is added to publish a message when a mousedown event occurs on the canvas. In the CanvasViewerSwitcher.vue file, a new function closePopover is introduced to manage the popover's visibility, and it is invoked during the handleSwitchPreview function and upon receiving the canvas-mousedown event.

Changes

File(s)	Change Summary
packages/canvas/container/src/CanvasContainer.vue	Added a line to publish a message on mousedown event using useMessage().publish({ topic: 'canvas-mousedown', data: { event } }).
packages/canvas/container/src/components/CanvasViewerSwitcher.vue	Introduced closePopover function to invoke popoverRef.value?.doClose(), updated handleSwitchPreview to call closePopover prior to its logic, and included it in the return object.

Possibly related PRs

• fix: TinyGrid slot children can not operate #1100: The changes in the main PR, which involve publishing a message on a mousedown event, are related to the retrieved PR's addition of a subscription to the same canvas-mousedown message, indicating a direct connection in event handling.
• fix(canvas/render): fix switching between top pages in standalone view mode, cssScope not updated and entry point pageContext active error #1044: The changes in the main PR, which involve publishing a message on a mousedown event, are related to the retrieved PR that subscribes to the same canvas-mousedown message to trigger a function, indicating a direct interaction between the two.
• fix: canvas srcdoc #856: The changes in the main PR, which involve publishing a message on a mousedown event, are related to the retrieved PR's addition of a subscription to the same canvas-mousedown message, indicating a direct connection in event handling between the two components.

Suggested labels

ready_for_review

Suggested reviewers

• chilingling
• hexqi

Poem

Hoppy clacks and fluttering keys,
I, a coding rabbit, bring the breeze.
Popovers vanish with a joyful hop,
Each ref and function—nonstop!
Celebrating changes with a carrot kiss! 🥕🐇

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/canvas/container/src/components/CanvasViewerSwitcher.vue

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "@typescript-eslint/eslint-plugin".

(The package "@typescript-eslint/eslint-plugin" was not found when loaded as a Node module from the directory "/packages/canvas".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install @typescript-eslint/eslint-plugin@latest --save-dev

The plugin "@typescript-eslint/eslint-plugin" was referenced from the config file in "packages/canvas/.eslintrc.cjs » @vue/eslint-config-typescript".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

---

📜 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 1d8878f and be47563.

📒 Files selected for processing (1)

• packages/canvas/container/src/components/CanvasViewerSwitcher.vue (3 hunks)

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

• packages/canvas/container/src/components/CanvasViewerSwitcher.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.