Fix:reset editor UI when creating a new project (#414)

[Abubakar2105]

Description

This PR resolves an issue where, after creating a new project, the editor UI continued to show the previous project's content until a manual refresh.

The logic to load the newly created project (loadProject(newProject.id)) already existed, but was not being invoked. This change simply calls the existing function after project creation to ensure the UI updates correctly.

Fixes #414

Type of change

• Bug fix (existing behavior was not wired correctly)

How Has This Been Tested?

• Created a new project
• Verified that the editor switches to the new project immediately
• Confirmed that old project content no longer appears

Test Configuration:

• Node version: 18.x
• Browser: Chrome 125
• OS: Windows 11

Screenshots (if applicable)

N/A

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if needed)
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes

Additional context

This doesn’t introduce new logic, just ensures existing loadProject is called when creating a new project, so the UI state aligns with the backend.

Summary by CodeRabbit

• Bug Fixes
  • Newly created projects are now fully loaded into the editor immediately after creation, ensuring all project details and media are available right away.

[netlify]

👷 Deploy request for appcut pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	515e283

[vercel]

@Abubakarashrafi is attempting to deploy a commit to the OpenCut OSS Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

"""

Walkthrough

The createNewProject method in the project store now calls loadProject(newProject.id) immediately after saving a new project and reloading the project list. This change ensures that the newly created project is loaded into the editor's state right after creation, preventing display of previous project contents.

Changes

File	Change Summary
apps/web/src/stores/project-store.ts	Added call to loadProject(newProject.id) in createNewProject to immediately load the new project

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ProjectStore
    participant Editor

    User->>ProjectStore: createNewProject()
    ProjectStore->>ProjectStore: save new project
    ProjectStore->>ProjectStore: reload project list
    ProjectStore->>ProjectStore: loadProject(newProject.id)
    ProjectStore->>Editor: update state with new project data

Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix: remove wrong check causing new project to show old medias #341: Both PRs address the loading behavior of a newly created project to ensure the editor state reflects the new project correctly, with the main PR adding an explicit load call after creation and the retrieved PR fixing a check that prevented proper loading, making their changes directly related.

Suggested reviewers

• simonorzel26

Poem

A project born, so fresh and bright,
Now loads its state, just right!
No ghostly clips from projects past,
The editor’s clean and new at last.
With every hop, a bug undone—
The rabbit’s work is never done! 🐇✨
"""

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 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 dc251fd and 515e283.

📒 Files selected for processing (1)

• apps/web/src/stores/project-store.ts (1 hunks)

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

• apps/web/src/stores/project-store.ts

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • 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? Create a ticket on our support page 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 docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests 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.

[Abubakar2105]

@mazeincoding
@simonorzel26
@izadoesdev

[khanguyen74]

Clean fix! However, it looks like your file uses different line endings (CRLF). We're using LF, which is why the whole file shows as changed. You might want to look into that.

[Tsurgcom]

Idk looks good to me