Enhancement : Geographic Details Auto-fill in Facility Creation Form

[Mahendar0701]

Proposed Changes

• Fixes Enhancement To Geographic Details Auto-fill in Facility Creation Form #10013

• Implement auto-fill functionality for the geographic details dropdowns (State, District, Local Body) in the "Create Facility" form based on the user's current organization page. For instance, if the user is on the "Aluva Municipality" organization page, the dropdowns should automatically populate with "Kerala" (State), "Ernakulam" (District), and "Aluva" (Local Body) when the form is opened.

• Ensure proper handling of pincode autofill behavior. When a user inputs a pincode that corresponds to a region outside the autofilled district (e.g., a non-Ernakulam district pincode while on the Aluva organization page), display a prompt confirming the change. The prompt should ask the user if they want to proceed with updating the State and District fields to reflect the new pincode (e.g., new State: Kerala, new District: Ernakulam).

• For the "Update Facility" page, ensure that dropdown values are fetched based solely on the facility's existing data. Do not consider the current organization page for auto-filling in this case.

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

• Add specs that demonstrate bug / test a new feature.
• Update product documentation.
• Ensure that UI text is kept in I18n files.
• Prep screenshot or demo video for changelog entry, and attach it to issue.
• Request for Peer Reviews
• Completion of QA

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[netlify]

✅ Deploy Preview for care-ohc ready!

Name	Link
🔨 Latest commit	f3c91a9
🔍 Latest deploy log	https://app.netlify.com/sites/care-ohc/deploys/678cb43d0976080008c6fdf6
😎 Deploy Preview	https://deploy-preview-10019--care-ohc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Mahendar0701]

@rithviknishad @Jacobjeevan The organization details are fetching and autofilling properly. But unnecessary api calls with trash values as organizationId are being called.

Am i missing something while using useQuery?

Edit : It happened due to incorrect parameter mapping in queryFn. Sry 😅

[Mahendar0701]

Ensure proper handling of pincode autofill behavior. When a user inputs a pincode that corresponds to a region outside the autofilled district (e.g., a non-Ernakulam district pincode while on the Aluva organization page), display a prompt confirming the change. The prompt should ask the user if they want to proceed with updating the State and District fields to reflect the new pincode (e.g., new State: Kerala, new District: Ernakulam).

@Nihal , @rithviknishad I think this feature may not be needed because:

• Allowing users to enter a mismatched pincode for a specific geography (e.g., Aluva) may lead to incorrect records.. It's better to ensure the pincode matches the organization’s location.
• If a user enters the different pincode, clearing the field already restores the correct autofill values, making additional prompts unnecessary.
• Facilities should remain tied to their correct geography to avoid confusion or incorrect records.

Correct me if i am wrong, i will take your input and will do suggested changes