feat: added confetti to the verification page using react-confetti library

[Niharika0104]

Related Issue

#152

Description

I have added a confetti animation on the verification page using react-confetti library.

Screenshots

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @Sanchitbajaj02 on Vercel.

@Sanchitbajaj02 first needs to authorize it.

[coderabbitai]

Walkthrough

This set of changes primarily focuses on enhancing user experience and code cleanliness. For user experience, a notable addition is the confetti animation on the verification page, providing a celebratory feedback upon successful verification. Code cleanliness improvements include formatting adjustments in environment variables and function bodies, renaming a variable for clarity, and minor adjustments in component dependencies. These changes do not alter the logic but improve the readability and user interface.

Changes

File Path	Change Summary
.env.example	Updated formatting of environment variable declarations.
src/.../verify/page.tsx	Added extra empty lines within the function body.
src/backend/appwrite.config.ts	Renamed NEXT_PUBLIC_USERS_COLLECTION to NEXT_PUBLIC_USER_COLLECTION.
src/backend/auth.api.ts	Added an extra newline before the function comment block.
src/components/core/navbar/index.tsx	Adjusted useEffect hook's dependency array formatting.
src/components/pages/auth/verification/index.tsx	Added confetti animation upon user verification.
src/components/pages/home/index.tsx	Inserted a blank line within the HomePage function.

Related issues

• Feat: Confetti animation on verified page #152: The addition of confetti animation on the verification page directly addresses the feature request for a celebratory effect upon successful verification.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit-tests for this file.
• 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 generate unit tests for this file.
  • @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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[github-actions]

Great job, @Niharika0104! 🎉 Thank you for submitting your pull request. Your contribution is valuable and we appreciate your efforts to improve our project. Keep being the part of the community!

'We will promptly review your changes and offer feedback. Keep up the excellent work!
Kindly remember to check our Contributing Guidelines'

[coderabbitai]

Review Status

Actionable comments generated: 2

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between a2c4a18 and 6b7b27c.

Files ignored due to path filters (3)

• package-lock.json is excluded by: !**/*.json
• package.json is excluded by: !**/*.json
• yarn.lock is excluded by: !**/*.lock

Files selected for processing (7)

• .env.example (1 hunks)
• src/app/(auth)/verify/page.tsx (1 hunks)
• src/backend/appwrite.config.ts (1 hunks)
• src/backend/auth.api.ts (1 hunks)
• src/components/core/navbar/index.tsx (1 hunks)
• src/components/pages/auth/verification/index.tsx (2 hunks)
• src/components/pages/home/index.tsx (2 hunks)

Files skipped from review due to trivial changes (1)

• src/app/(auth)/verify/page.tsx

Additional comments: 4

src/backend/appwrite.config.ts (1)

• 14-14: The variable renaming from NEXT_PUBLIC_USERS_COLLECTION to NEXT_PUBLIC_USER_COLLECTION improves consistency in naming conventions. Ensure all references to this variable across the codebase have been updated accordingly.

Verification successful

---

The variable renaming from NEXT_PUBLIC_USERS_COLLECTION to NEXT_PUBLIC_USER_COLLECTION appears to have been correctly updated across all TypeScript files in the codebase, as no references to the old variable name were found. This suggests the change has been successfully implemented without issues.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Search for old variable name to ensure it's been updated everywhere.
rg --type ts "NEXT_PUBLIC_USERS_COLLECTION"

Length of output: 43

src/components/pages/home/index.tsx (1)

• 21-21: The addition of a blank line improves code readability by visually separating different sections within the useEffect hook.

src/backend/auth.api.ts (1)

• 6-6: The addition of an extra newline before the function comment block enhances code readability by clearly separating import statements from function definitions.

src/components/core/navbar/index.tsx (1)

• 82-82: Removing unnecessary spaces in the dependency array of the useEffect hook improves code cleanliness and consistency.

[Sanchitbajaj02]

LGTM, merging