Fix kvCORE email parsing

[preritdas]

Was previously using an incorrect mechanism of retrieving a lead's email addresses.

Summary by CodeRabbit

• New Features

  • Introduced a new test file to validate the email body generation in the KVCoreDeliverer class.
  • Added functionality to generate random names for testing purposes.

• Bug Fixes

  • Updated the construction of the email body to improve how emails are represented in the output.

• Tests

  • Implemented basic tests for the KVCoreDeliverer to ensure expected personal information fields are included in the email body.
  • Removed outdated functions and fixtures from existing test files to streamline the testing setup.

[coderabbitai[bot]]

[!CAUTION]

Review failed

The pull request is closed.

Walkthrough

The pull request introduces modifications to the email body construction in the _email_body method of the real_intent/deliver/kvcore/__init__.py file. Additionally, it adds a new function and a pytest fixture in tests/conftest.py for generating random names and sample PII data, respectively. The changes also involve the removal of previously defined functions and fixtures in tests/test_followupboss.py. A new test file, tests/test_kvcore.py, is created to validate the email body generation of the KVCoreDeliverer class.

Changes

Files	Change Summary
real_intent/deliver/kvcore/__init__.py	Modified the _email_body method to change how the email is constructed by appending the first email object instead of its email attribute.
tests/conftest.py | Addedgenerate_random_name(length=6)function andsample_pii_md5s` pytest fixture for generating random names and structured PII data for testing.
tests/test_followupboss.py | Removedgenerate_random_namefunction andsample_pii_md5s` fixture.
tests/test_kvcore.py | Introduced new tests forKVCoreDeliverer`, specifically validating the email body generation with assertions on personal information fields.

Possibly related PRs

• 95: The changes in this PR also modify the _email_body method in the real_intent/deliver/kvcore/__init__.py file, which is directly related to the changes made in the main PR regarding how the email body is constructed.

🐰 In a world of code and light,
A rabbit hops with joy so bright.
New names to share, and tests to run,
Email bodies crafted, oh what fun!
With every change, we leap and cheer,
For better code is finally here! 🐇✨

---

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: -- `I pushed a fix in commit , please review it.` -- `Generate unit testing code for this file.` - `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 generate unit testing code 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 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 generate unit testing code.` -- `@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.` 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 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

Early access features: enabled