fix: Widget Selection prompts showing outside Editor

[hetunandu]

Description

When canvas is shown outside the Editor State, we are still showing the canvas with widget selection prompts. Outside the editor, the canvas can be interactable but not selectable.

Fixes #32444

Automation

/ok-to-test tags="@tag.IDE, @tag.Widget, @tag.MobileResponsive, @tag.Anvil"

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8750634714
Commit: 0ca531f
Cypress dashboard url: Click here!

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• New Features
  • Enhanced the Widgets Editor to conditionally display elements based on the current editor state.
  • Improved interaction in the IDE by focusing on widgets only when in the editor state.

[coderabbitai]

Walkthrough

The changes involve implementing state checks using useCurrentAppState and EditorState to conditionally render components and manage interactions based on the IDE's current state. This ensures that interactions like widget focusing and tooltips are appropriately controlled within the editor mode.

Changes

File Path	Change Summary
.../CodeModeTooltip.tsx	Conditionally renders children if the editor state is EditorState.EDITOR.
.../useHoverToFocusWidget.ts	Added state checks to conditionally focus on widgets based on the IDE state, enhancing interaction management.

Assessment against linked issues

Objective	Addressed	Explanation
Prevent tooltip from showing up in settings (#32444)	✅
Prevent widget interaction in edit mode by checking IDE state (#32138)	❌	The changes do not include any mechanism to disable widget interaction as described in the issue.
Address modal widget interaction issues when multiple modals are open (#30653)	❌	The PR does not address modal widget interactions or stacking order issues.

Possibly related issues

• Restrict Widget Interaction in Edit Mode #32138: The changes include adding state checks which could be extended or modified to prevent widget interactions in edit mode as described in the issue.
• [Bug]: WDS Modal critical issues #30653: Although not directly addressed, the management of IDE states in the PR could indirectly influence modal widget behaviors, especially in complex interaction scenarios.

---

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>.
  • 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 show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.