update to have the ability to relaunch after 7 days

[khaledtf19]

Description

Brief description of what this PR does:

Type of Change

• 🐛 Bug fix
• ✨ New feature
• 📝 Documentation update
• 🎨 Style/UI update
• ⚡ Performance improvement
• Other (please describe)

Testing

• I have tested my changes locally

Checklist

• My code follows the project style
• I've updated relevant documentation

Screenshots (if applicable)

Add any relevant screenshots here

---

Please ensure your PR title clearly describes the change.

Summary by CodeRabbit

• New Features

  • Added a time-based restriction for relaunching projects, requiring at least 7 days between launches. Users attempting to relaunch too soon will receive a message indicating how many days remain before they can relaunch.

• Bug Fixes

  • Multiple launches for the same project are now permitted, allowing for a more flexible relaunch process.

[vercel]

@khaledtf19 is attempting to deploy a commit to the ossdotnow Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

This change updates the project launch logic to enforce a 7-day cooldown between launches by modifying the mutation to check the most recent launch date and reject new launches if the cooldown has not expired. Additionally, it removes the unique constraint on the projectId column in the project launches database schema, allowing multiple launch records per project.

Changes

Cohort / File(s)	Change Summary
API mutation update packages/api/src/routers/launches.ts	Adds 7-day cooldown logic to the launchProject mutation, using differenceInDays from date-fns to enforce time-based restrictions on relaunching projects.
Database schema update packages/db/src/schema/project-launches.ts	Removes the unique constraint on projectId in the projectLaunch table schema, allowing multiple launches per project.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant API
    participant DB

    User->>API: Request launchProject(projectId)
    API->>DB: Query latest launch for projectId
    DB-->>API: Return latest launch (if any)
    API->>API: Calculate days since last launch
    alt Less than 7 days
        API-->>User: Throw conflict error with days remaining
    else 7 days or more (or no prior launch)
        API->>DB: Insert new launch record
        DB-->>API: Confirm insertion
        API-->>User: Return success
    end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• feat: implement project launch scheduling and update project linking #167: Adds frontend scheduling UI and backend validation for launch dates/times, as well as database changes for launch scheduling. Related due to overlapping areas in launch timing logic and mutation handling.

Poem

A project waits, the clock ticks slow,
Seven days must pass before next go.
No longer unique, launches may stack,
But patience is key—no turning back!
With code and care, the rules are set,
A rabbit cheers, "No cooldown regret!" 🐇✨

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 dae53ca and 2d646b0.

📒 Files selected for processing (2)

• packages/api/src/routers/launches.ts (2 hunks)
• packages/db/src/schema/project-launches.ts (1 hunks)

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

• packages/db/src/schema/project-launches.ts
• packages/api/src/routers/launches.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.