Skip to content

fix: prevent new project show old media in initial load#465

Closed
khanguyen74 wants to merge 1 commit into
OpenCut-app:mainfrom
khanguyen74:fix/new-project-has-old-media
Closed

fix: prevent new project show old media in initial load#465
khanguyen74 wants to merge 1 commit into
OpenCut-app:mainfrom
khanguyen74:fix/new-project-has-old-media

Conversation

@khanguyen74
Copy link
Copy Markdown
Contributor

@khanguyen74 khanguyen74 commented Jul 26, 2025

Description

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Test Configuration:

  • Node version:
  • Browser (if applicable):
  • Operating System:

Screenshots (if applicable)

Before

Screen.Recording.2025-07-17.at.7.18.06.PM.mov

After

Screen.Recording.2025-07-17.at.7.18.31.PM.mov

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have added screenshots if ui has been changed
  • 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

Additional context

Add any other context about the pull request here.

Summary by CodeRabbit

  • Bug Fixes
    • Improved error handling when loading a project fails; users are now redirected to the projects page if the project is not found, instead of creating a new project.
  • Refactor
    • Simplified project loading logic for better reliability and maintainability.

@netlify
Copy link
Copy Markdown

netlify Bot commented Jul 26, 2025

👷 Deploy request for appcut pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 76ba65c

@vercel
Copy link
Copy Markdown

vercel Bot commented Jul 26, 2025

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

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 26, 2025

Walkthrough

The code refactors the project loading logic in the editor page by removing dependencies on activeProject, createNewProject, and the tracking of handled project IDs. On failure to load a project, it now redirects to the projects list if the error indicates "not found," without attempting to create a new project.

Changes

File(s) Change Summary
apps/web/src/app/editor/[project_id]/page.tsx Removed use of activeProject, createNewProject, and handled project ID tracking; simplified error handling and effect dependencies.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant EditorPage
    participant ProjectStore

    User->>EditorPage: Navigates to /editor/[project_id]
    EditorPage->>ProjectStore: loadProject(project_id)
    alt Project found
        ProjectStore-->>EditorPage: Project data
    else Project not found
        ProjectStore-->>EditorPage: Error ("not found")
        EditorPage->>User: Redirect to /projects
    end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

Suggested reviewers

  • simonorzel26

Poem

A project page once checked IDs,
And spawned new ones with rabbit speed.
Now, if not found, it hops away,
Redirects you to projects—no delay!
Simpler logic, lighter load,
The editor takes a streamlined road.
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

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

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

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
apps/web/src/app/editor/[project_id]/page.tsx (1)

46-50: Good fix! Consider making error handling more robust.

The new error handling correctly addresses the bug by redirecting to the projects list instead of creating a new project that could inherit old media. This is much cleaner than the previous approach.

Consider making the error handling more robust by checking error status codes in addition to message content:

-        if (error.message.includes("not found")) {
+        if (error.message.includes("not found") || error.status === 404) {
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 14475dc and 76ba65c.

📒 Files selected for processing (1)
  • apps/web/src/app/editor/[project_id]/page.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build (windows-latest)
🔇 Additional comments (2)
apps/web/src/app/editor/[project_id]/page.tsx (2)

35-35: LGTM! Simplification addresses the core issue.

Removing activeProject and createNewProject from the store destructuring eliminates potential sources of stale state that could cause old media to persist in new projects. This directly addresses the PR objective.


56-56: Dependency array correctly reflects the simplified logic.

The updated dependency array properly includes only the values actually used in the effect (projectId, loadProject, router) and removes dependencies that were causing the old media bug. This should make the effect more predictable and performant.

@Abubakar2105
Copy link
Copy Markdown

I also have open pr for that issue you can check #427

@khanguyen74 khanguyen74 reopened this Jul 26, 2025
@khanguyen74
Copy link
Copy Markdown
Contributor Author

Closed in favor of #427

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants