Update correct spelling

[belwalshubham]

Description

Fixed the seplling of permanently closed to parmanently closed

Summary by CodeRabbit

• Bug Fixes
  • Corrected a typo in the status name for dropping centers, ensuring accurate filtering for feedback emails.
  • Adjusted query conditions to use the correct status name, improving data retrieval accuracy for dropping center statuses.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces corrections to query conditions in two PHP files, specifically targeting the status name for dropping centers. The BiannualDroppingCenterFeedbackCron.php and FeedbackDroppingCenterCron.php files have been updated to replace the incorrect status 'Permanently_Closed' with 'Parmanently_Closed'. These changes ensure that the logic for sending feedback emails to dropping centers aligns with the intended functionality. The overall control flow and error handling mechanisms remain unchanged.

Changes

File Path	Change Summary
wp-content/civi-extensions/goonjcustom/api/v3/Goonjcustom/BiannualDroppingCenterFeedbackCron.php	Corrected the status name from 'Permanently_Closed' to 'Parmanently_Closed' in the query condition.
wp-content/civi-extensions/goonjcustom/api/v3/Goonjcustom/FeedbackDroppingCenterCron.php	Corrected the status name from 'Permanently_Closed' to 'Parmanently_Closed' in the query condition.

Possibly related PRs

• Change the type of custom field #319: This PR involves a correction in the query condition for the status of dropping centers, changing 'Permanently_Closed' to 'Parmanently_Closed', similar to the typo correction in the main PR.
• Send Feedback Email When Dropping Center is Closed or sent every 6 month #393: This PR implements an automated feedback email system that activates when a Dropping Center's status is changed to "Permanently Closed", which relates to the status checks in the main PR.
• Do Not Send Feedback Emails for Closed Status in Biannual Cron #399: This PR modifies the biannual cron job to prevent sending feedback emails for dropping centers that are closed, directly connecting to the status logic in the main PR.
• Dropping Center Feedback Cron Fixes #397: This PR includes fixes related to the feedback cron functionality, specifically updating how the feedback email delivery status is processed, which aligns with the changes made in the main PR.

🎉 In the code where the status was wrong,
A typo was fixed, and now it’s strong!
Feedback emails will flow with grace,
To dropping centers in their rightful place.
With 'Parmanently_Closed' now in sight,
The logic shines, everything’s right! 🌟

---

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>, 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.