Notify user of unsaved changes before unloading

[k0d13]

Summary by CodeRabbit

• New Features

  • Added a warning prompt to prevent users from accidentally leaving the page when there are unsaved changes in the explorer.

• Bug Fixes

  • Improved detection of changes within the explorer to better track unsaved modifications.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
evaluate	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 12, 2025 1:44pm

[coderabbitai]

Walkthrough

The updates introduce a mechanism in the explorer component to track unsaved changes in the root folder and prevent accidental page unloads when changes are present. Additionally, a type assertion is added to the schema resolver in the execute bar component's form initialization. No public API signatures are altered.

Changes

File(s)	Change Summary
apps/website/src/components/editor/execute-bar/index.tsx	Casts the ExecuteOptions schema to never when passing to zodResolver in the useForm hook initialization.
apps/website/src/components/explorer/use.tsx	Adds hasChange state, subscribes to root folder changes, and blocks page unload if there are unsaved changes.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Browser
    participant ExplorerProvider
    participant RootFolder

    User->>ExplorerProvider: Make changes (add/remove child)
    ExplorerProvider->>RootFolder: Listen for 'child' change events
    RootFolder-->>ExplorerProvider: Emits 'child' change event
    ExplorerProvider->>ExplorerProvider: Set hasChange = true

    Browser->>ExplorerProvider: beforeunload event
    alt hasChange is true
        ExplorerProvider->>Browser: Prevent unload, show warning
    else hasChange is false
        ExplorerProvider->>Browser: Allow unload
    end

Loading

Poem

A folder changed, a warning raised,
The rabbit hops, quite unphased.
"Don't leave just yet!" the browser pleads,
For unsaved work, attention it needs.
With type casts neat and changes caught,
The code is safe—just as it ought!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f9c1345 and df10a1a.

📒 Files selected for processing (2)

• apps/website/src/components/editor/execute-bar/index.tsx (1 hunks)
• apps/website/src/components/explorer/use.tsx (1 hunks)

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in 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.