fix email issue

[ank1traj]

Description

Fix the issue causing email to get failed and few enhancements.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [ ] Test A
• [ ] Test B

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my own code
• [ ] 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

Summary by CodeRabbit

• New Features

  • Introduced event trigger for pull requests marked "ready_for_review."
  • Enhanced user feedback with toast notifications for email verification success or failure.

• Bug Fixes

  • Updated error messages for email sending failures to be more concise.
  • Changed button text to reflect copy status more clearly across various components.
  • Refactored email sending logic for improved error handling.

• Documentation

  • No visible changes to end-users.

• Refactor

  • Adjusted JSX structure in sign-in and sign-up pages for better code readability.

• Style

  • Minor reformatting of JSX elements' indentation and nesting.

• Tests

  • No visible changes to end-users.

• Chores

  • Initialized LogRocket upon user sign-in status change.

• Revert

  • No reverts in this pull request.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
testcase-generator	✅ Ready (Inspect)	Visit Preview	Dec 26, 2023 5:35pm

[coderabbitai[bot]]

Walkthrough

The changes involve UI improvements, better error handling, and code readability enhancements. Triggers for pull requests and issue assignments in GitHub workflows were adjusted, while button texts across various components were standardized for clarity. The email functionality received a more user-friendly toast notification system and cleaner code with async/await syntax. The project's sign-in page now integrates LogRocket for user tracking, providing a smoother experience and better monitoring.

Changes

File Path	Change Summary
.github/workflows/action.yml	Added trigger for pull requests marked as "ready_for_review."
.github/workflows/take_issue.yml	Fixed indentation under name: Assign issue to contributor.
components/generator/.../arrayGenerator.js components/generator/.../integerGenerator.js components/generator/.../linkedListGenerator.js components/generator/.../palindromeGenerator.js components/generator/.../stringGenerator.js	Updated button text for consistency and removed a console.log statement.
components/generator/.../arrayGeneratorFunc.js	Changed error message text for email sending failure.
config/nodemailer.js	Enhanced email transporter setup with toast notifications and improved code structure.
lib/api.js	Refactored sendConfirmation to use async/await and added toast notifications.
pages/api/confirm.js	Modified email sending logic, switching to and from fields.
pages/index.js	Added useEffect for isSignedIn state and LogRocket initialization.
pages/sign-in/[[...index]].jsx pages/sign-up/[[...index]].jsx	Reformatted JSX structure for better readability; no logic change.

🐇🌟 "In the warren of the web, the CodeRabbit hopped,
Tweaking workflows and UI, never stopped.
Where emails fly and buttons gleam,
A burrow of code, refactored clean." 🌱🖥️

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

---

Tips

### Chat with CodeRabbit Bot (`@coderabbitai`) - You can directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit-tests for this file.` - You can tag CodeRabbit on specific lines of code or entire files in the PR by tagging `@coderabbitai` in a comment. Examples: - `@coderabbitai generate unit tests for this file` - `@coderabbitai modularize this function` - You can tag `@coderabbitai` in a PR comment and ask questions about the PR and the codebase. Examples: - `@coderabbitai gather interesting statistics about this repository and render them in a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai generate unit tests for the src/utils.ts file.` ### 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](https://coderabbit.ai/integrations/coderabbit-overrides.v2.json). - 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](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback.

[ghost]

👇 Click on the image for a new way to code review

#### [](https://app.codesee.io/r/reviews?pr=40&src=https%3A%2F%2Fgithub.com%2FWebSorcery%2Ftestcase-generator) #### Legend

[gitstream-cm[bot]]

This PR is missing a Jira ticket reference in the title or description. Please add a Jira ticket reference to the title or description of this PR.