Skip to content

Optimize State Field for Dropping Center Form to Show Only Indian States#385

Merged
belwalshubham merged 1 commit intodevelopfrom
feature/indian-states-filter
Oct 19, 2024
Merged

Optimize State Field for Dropping Center Form to Show Only Indian States#385
belwalshubham merged 1 commit intodevelopfrom
feature/indian-states-filter

Conversation

@belwalshubham
Copy link
Copy Markdown
Collaborator

@belwalshubham belwalshubham commented Oct 19, 2024

PR Description:

This update enhances the Dropping Center form by ensuring the State field displays only Indian states. The implementation includes the following:

  • Added logic to filter and display only active Indian states in the State dropdown.

Summary by CodeRabbit

  • New Features

    • Introduced functionality to handle Indian state options dynamically within the dropping center service.
    • Added support for filtering and retrieving active Indian states for relevant fields.
  • Bug Fixes

    • Improved event handling by incorporating a new event hook for field options related to Indian states.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Oct 19, 2024

Walkthrough

The changes in this pull request enhance the DroppingCenterService class by introducing new functionality related to Indian state options. A new import for Civi\Api4\StateProvince has been added, and the getSubscribedEvents method now includes a hook for handling field options. A new method, setIndianStateOptions, is defined to populate options for a custom state field when the entity is Eck_Collection_Camp, allowing for dynamic retrieval of active Indian states.

Changes

File Path Change Summary
wp-content/civi-extensions/goonjcustom/Civi/DroppingCenterService.php - Added import for Civi\Api4\StateProvince.
- Updated getSubscribedEvents to include &hook_civicrm_fieldOptions.
- Added method setIndianStateOptions to handle Indian state options for Eck_Collection_Camp.

Possibly related PRs

Suggested labels

status : ready for review

Suggested reviewers

  • pokhiii

🎉 In the land of code where changes flow,
The DroppingCenterService now steals the show.
With states from India, options abound,
In the realm of events, new hooks are found.
A method to set, a feature so bright,
Enhancing our service, it feels just 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
🪧 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.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 6c6d942 and fdebd5e.

📒 Files selected for processing (1)
  • wp-content/civi-extensions/goonjcustom/Civi/DroppingCenterService.php (3 hunks)
🧰 Additional context used
🔇 Additional comments (2)
wp-content/civi-extensions/goonjcustom/Civi/DroppingCenterService.php (2)

10-10: Import statement looks good!

The new import for Civi\Api4\StateProvince is correctly placed and relevant to the new functionality being added.


39-39: New event hook added correctly!

The '&hook_civicrm_fieldOptions' => 'setIndianStateOptions' hook has been properly added to the getSubscribedEvents method. It follows the existing naming convention and is associated with the newly added method.

Comment on lines +421 to +453
public static function setIndianStateOptions(string $entity, string $field, array &$options, array $params) {
if ($entity !== 'Eck_Collection_Camp') {
return;
}

$customStateFields = CustomField::get(FALSE)
->addWhere('custom_group_id:name', '=', 'Dropping_Centre')
->addWhere('name', '=', 'State')
->execute();

$stateField = $customStateFields->first();

$stateFieldId = $stateField['id'];

if ($field !== "custom_$stateFieldId") {
return;
}

$activeIndianStates = StateProvince::get(FALSE)
->addWhere('country_id.iso_code', '=', 'IN')
->addOrderBy('name', 'ASC')
->execute();

$stateOptions = [];
foreach ($activeIndianStates as $state) {
if ($state['is_active']) {
$stateOptions[$state['id']] = $state['name'];
}
}

$options = $stateOptions;

}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Good implementation, but room for improvement

The setIndianStateOptions method is well-structured and follows the single responsibility principle. However, consider the following suggestions:

  1. Move the filtering of active states to the API call for better efficiency:
 $activeIndianStates = StateProvince::get(FALSE)
   ->addWhere('country_id.iso_code', '=', 'IN')
+  ->addWhere('is_active', '=', TRUE)
   ->addOrderBy('name', 'ASC')
   ->execute();

 $stateOptions = [];
 foreach ($activeIndianStates as $state) {
-  if ($state['is_active']) {
-    $stateOptions[$state['id']] = $state['name'];
-  }
+  $stateOptions[$state['id']] = $state['name'];
 }
  1. Consider adding error handling for API calls to improve robustness.

  2. The custom field retrieval could be moved to a separate method for better reusability and to adhere to the DRY principle.

Would you like me to provide a more detailed refactoring suggestion for these improvements?

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
public static function setIndianStateOptions(string $entity, string $field, array &$options, array $params) {
if ($entity !== 'Eck_Collection_Camp') {
return;
}
$customStateFields = CustomField::get(FALSE)
->addWhere('custom_group_id:name', '=', 'Dropping_Centre')
->addWhere('name', '=', 'State')
->execute();
$stateField = $customStateFields->first();
$stateFieldId = $stateField['id'];
if ($field !== "custom_$stateFieldId") {
return;
}
$activeIndianStates = StateProvince::get(FALSE)
->addWhere('country_id.iso_code', '=', 'IN')
->addOrderBy('name', 'ASC')
->execute();
$stateOptions = [];
foreach ($activeIndianStates as $state) {
if ($state['is_active']) {
$stateOptions[$state['id']] = $state['name'];
}
}
$options = $stateOptions;
}
public static function setIndianStateOptions(string $entity, string $field, array &$options, array $params) {
if ($entity !== 'Eck_Collection_Camp') {
return;
}
$customStateFields = CustomField::get(FALSE)
->addWhere('custom_group_id:name', '=', 'Dropping_Centre')
->addWhere('name', '=', 'State')
->execute();
$stateField = $customStateFields->first();
$stateFieldId = $stateField['id'];
if ($field !== "custom_$stateFieldId") {
return;
}
$activeIndianStates = StateProvince::get(FALSE)
->addWhere('country_id.iso_code', '=', 'IN')
->addWhere('is_active', '=', TRUE)
->addOrderBy('name', 'ASC')
->execute();
$stateOptions = [];
foreach ($activeIndianStates as $state) {
$stateOptions[$state['id']] = $state['name'];
}
$options = $stateOptions;
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants