test: add notify route delete coverage

[pari-28]

Description

Fixes #4433

Added app/api/notify/route.delete.test.ts to provide isolated test coverage for the notify DELETE endpoint.

Added Test Coverage

• Missing user parameter validation
• Rate limiting behavior
• Development-mode bypass when database configuration is unavailable
• Notification preference not found handling
• Successful notification preference deletion

Validation

• Added 5 test cases
• Verified locally using Vitest
• All tests passing successfully

Pillar

• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

N/A (test-only change)

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally.
• I have run npm run format and npm run lint locally and resolved all errors.
• My commits follow the Conventional Commits format.
• I have updated README.md if required. (Not applicable)
• I have started the repo.
• I have made sure that I have only one commit to merge in this PR.
• The SVG output matches the CommitPulse "premium quality" aesthetic standard. (Not applicable)
• (Recommended) I joined the CommitPulse Discord community.

[vercel]

@pari-28 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Aamod-Dev]

Thanks for the PR. I am requesting changes because this applies 'theme contrast' coverage to the 'notify' API route. Server-side API routes do not render any interactive DOM elements or CSS properties, making it impossible to test them for light and dark modes. Please target theme contrast tests to frontend UI components exclusively.

[Aamod-Dev]

Thanks for the contribution. I went through the changes and the overall approach looks good, but there are a few issues that should be addressed before this can be merged. Most of the concerns are related to correctness and maintainability. Please take a look at the points below and update the PR accordingly.

• The test targets an API route, which handles backend logic and does not have a user interface. Testing visual theme contrast here is not applicable.
• It appears the tests rely on asserting local hardcoded variables against themselves rather than exercising the actual application logic.

Once these issues are addressed, I'll be happy to take another look. Thanks again for the contribution.

[Aamod-Dev]

Thanks for putting this together. The code looks clean and solves the issue effectively.

No concerns from my end. Approved.

[Aamod-Dev]

This PR is currently marked with the \status:blocked\ label. Please resolve the blockers so we can proceed with a full review and approval.

[Aamod-Dev]

Thanks for the contribution! I went through the changes and have evaluated them according to the rubric.

[github-actions]

📦 Next.js Bundle Size Report (Gzipped Sizes)

✨ No significant bundle size changes detected.

📊 Summary of Totals

Category	PR Size	Base Size	Difference
Total JS	3405.30 KB	3405.30 KB	0 B
Total CSS	252.94 KB	252.94 KB	0 B

[Aamod-Dev]

Excellent test coverage! I went through the changes and covering the deletion routes for notifications secures user privacy and state consistency.
Labels applied:

• level:advanced: Simulating complex route deletions.
• quality:clean: Perfect assertions.
• ype:feature, ype:testing: Ensures notification lifecycle safety.

[github-actions]

🎉 Congratulations @pari-28! Your PR has been successfully merged. 🚀

Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.

⚠️ Important for GSSoC Contributors:
You are strictly advised to join our Discord Server as it is mandatory for all GSSoC participants. All important announcements, point claims, and community discussions happen there.

Keep building! 💻✨