Skip to content

Added logs for debugging#484

Merged
nishant22029 merged 1 commit intodevelopfrom
fix/added-log-for-debugging
Nov 22, 2024
Merged

Added logs for debugging#484
nishant22029 merged 1 commit intodevelopfrom
fix/added-log-for-debugging

Conversation

@nishant22029
Copy link
Copy Markdown
Collaborator

@nishant22029 nishant22029 commented Nov 22, 2024

  • Added logs for debugging

Summary by CodeRabbit

  • New Features
    • Enhanced logging for induction activities and email notifications.
  • Bug Fixes
    • Improved logic for handling email notifications related to induction activities, ensuring accurate status updates.
  • Refactor
    • Streamlined the method for checking email status in relation to activity updates.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Nov 22, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request involve modifications to the InductionService class within Civi/InductionService.php. Key updates include the addition of logging for induction activities and email notifications, particularly in the sendInductionRescheduleEmail method. The logic for determining email notifications has been inverted, affecting how induction activities are updated. Furthermore, the handleRescheduleEmailActivity method now retrieves email status directly from the Contact entity, streamlining the process of updating activity statuses.

Changes

File Path Change Summary
wp-content/civi-extensions/goonjcustom/Civi/InductionService.php - Added logging statements in sendInductionRescheduleEmail for notVisitedInductionActivities and contacts.
- Inverted logic for checking if an email was sent in sendInductionRescheduleEmail.
- Modified handleRescheduleEmailActivity to retrieve email status from Contact entity instead of existing email activity.

Possibly related PRs

Suggested reviewers

  • belwalshubham
  • tarunnjoshi

🎉 In the code where emails flow,
Logging helps us see the show!
Reschedules now with status clear,
Induction updates, have no fear!
With each change, we pave the way,
For smoother tasks, come what may! 🌟


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
🪧 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>, 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 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 for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@nishant22029 nishant22029 merged commit 0ed8479 into develop Nov 22, 2024
@nishant22029 nishant22029 deleted the fix/added-log-for-debugging branch November 22, 2024 09:47
@coderabbitai coderabbitai bot mentioned this pull request Jun 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant