feat: Change max to 5 for cp images

[BretRen]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@BretRen has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 45 minutes and 44 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 45 minutes and 44 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 87c83eee-52dd-47ca-a41f-36d0ec25969e

📥 Commits

Reviewing files that changed from the base of the PR and between 6eb913f and 433f362.

📒 Files selected for processing (2)

• migrations/1776675571_updated_cps.go
• website/src/routes/create/+page.svelte

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/change-to-5-of-max

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request increases the maximum number of images allowed for a collection from 3 to 5. This change includes a database migration to update the collection schema and a corresponding update to the client-side validation logic on the creation page. Feedback suggests extending this validation to the edit page to maintain consistency across the application.

[gemini-code-assist]

The validation for the maximum number of images (5) should also be implemented in the edit page (website/src/routes/edit/cps/[id]/+page.svelte) to maintain consistency across the application. Currently, the edit page lacks this client-side check, which could result in a poor user experience where the backend rejects the update without immediate feedback in the UI.