Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/google maps link #10003

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from

Conversation

rahulharpal1603
Copy link

@rahulharpal1603 rahulharpal1603 commented Jan 15, 2025

Proposed Changes

@ohcnetwork/care-fe-code-reviewers

Demo Video:

2025-01-16.02-17-42.mp4

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

Summary by CodeRabbit

  • New Features

    • Added Google Maps link for facilities with geographical coordinates
    • Enhanced localization support with Google Maps label
  • Documentation

    • Updated facility data type to include latitude and longitude properties

@rahulharpal1603 rahulharpal1603 requested a review from a team as a code owner January 15, 2025 20:49
Copy link
Contributor

coderabbitai bot commented Jan 15, 2025

Walkthrough

The pull request introduces a feature to add a Google Maps link for facilities by extending the FacilityData interface with latitude and longitude properties. The changes include updating the localization file, modifying the FacilityHome component to render a Google Maps link when coordinates are available, and adding new type definitions for facility data. This enhancement allows users to directly access the facility's location on Google Maps.

Changes

File Change Summary
public/locale/en.json Added new localization entry for "Google Maps"
src/types/facility/facility.ts Extended FacilityData interface with latitude and longitude properties
src/components/Facility/FacilityHome.tsx Added Google Maps link rendering with SquareArrowOutUpRight icon

Assessment against linked issues

Objective Addressed Explanation
Add Google Maps link for facility [#10000]
Use latitude and longitude from API
Link to exact location on Google Maps

Poem

🐰 A rabbit's map adventure calls,
Coordinates dance, Google Maps enthralls!
With latitude and longitude so bright,
We'll hop to locations, pure delight!
Mapping magic, just one click away! 🗺️


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fa95cbc and 1c1731e.

📒 Files selected for processing (1)
  • src/components/Facility/FacilityHome.tsx (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/components/Facility/FacilityHome.tsx

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

Copy link

netlify bot commented Jan 15, 2025

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit 1c1731e
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/6788a02cd574b300085c40be
😎 Deploy Preview https://deploy-preview-10003--care-ohc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@rahulharpal1603
Copy link
Author

@rithviknishad Kindly review this.

Copy link
Contributor

@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

🧹 Nitpick comments (1)
src/types/facility/facility.ts (1)

31-32: Consider using number type for geographical coordinates.

The latitude and longitude properties are currently typed as string, but they represent numerical values. Consider:

  1. Using number type instead of string for better type safety and to avoid unnecessary string-to-number conversions.
  2. Adding validation constraints using JSDoc or custom type guards to ensure valid coordinate ranges:
    • Latitude: -90 to 90
    • Longitude: -180 to 180
-  latitude: string;
-  longitude: string;
+  /** Latitude in decimal degrees, range: -90 to 90 */
+  latitude: number;
+  /** Longitude in decimal degrees, range: -180 to 180 */
+  longitude: number;
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3e98ab7 and fa95cbc.

📒 Files selected for processing (8)
  • public/locale/en.json (1 hunks)
  • public/locale/hi.json (1 hunks)
  • public/locale/kn.json (1 hunks)
  • public/locale/ml.json (1 hunks)
  • public/locale/mr.json (1 hunks)
  • public/locale/ta.json (1 hunks)
  • src/components/Facility/FacilityHome.tsx (3 hunks)
  • src/types/facility/facility.ts (1 hunks)
🔇 Additional comments (8)
src/components/Facility/FacilityHome.tsx (2)

287-297: LGTM! Well-implemented Google Maps link.

The implementation:

  • Correctly checks for both latitude and longitude before rendering
  • Uses proper security attributes (target="_blank" with rel="noreferrer")
  • Follows accessibility best practices with proper text and icon

281-281: LGTM! Margin adjustment.

The margin adjustment from mt-2 to mt-1 improves the visual spacing.

public/locale/mr.json (1)

42-42: LGTM! Correct Marathi translation.

The translation "Google नकाशे" is appropriate and consistent with Marathi language conventions.

public/locale/hi.json (1)

395-395: LGTM! Correct Hindi translation.

The translation "Google मैप्स" is appropriate and consistent with Hindi language conventions.

public/locale/kn.json (1)

397-397: Translation looks good!

The Kannada translation "Google ನಕ್ಷೆಗಳು" is accurate and follows proper localization practices.

public/locale/ta.json (1)

396-396: Translation looks good!

The Tamil translation "Google வரைபடங்கள்" is accurate and follows proper localization practices.

public/locale/ml.json (1)

998-998: LGTM! Translation looks good.

The Malayalam translation for "Google Maps" is accurate and consistent with the translations added in other locale files.

public/locale/en.json (1)

1081-1081: LGTM! The translation key follows the established conventions.

The addition of the "google_maps" translation key with value "Google Maps" is consistent with the existing naming patterns and properly handles the capitalization of the proper noun.

src/components/Facility/FacilityHome.tsx Outdated Show resolved Hide resolved
@rajku-dev
Copy link
Contributor

rajku-dev commented Jan 16, 2025

@rahulharpal1603 Do not add translations for all languages except en.json
Refer https://github.com/ohcnetwork/care_fe?tab=readme-ov-file#translations

@github-actions github-actions bot added needs-triage question Further information is requested labels Jan 16, 2025
@rahulharpal1603
Copy link
Author

@rahulharpal1603 Do not add translations for all languages except en.json
Refer https://github.com/ohcnetwork/care_fe?tab=readme-ov-file#translations

Thanks, I will fix it

@rithviknishad rithviknishad added needs testing needs review and removed question Further information is requested needs-triage labels Jan 17, 2025
@nihal467
Copy link
Member

LGTM

Copy link
Member

@rithviknishad rithviknishad left a comment

Choose a reason for hiding this comment

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

I could be wrong, but from product perspective, I don't see any use case for adding this here. Authenticated users would definitely be inside the facility itself right?
This would've added value if it was in the public page where patients get to see the facility details.

cc: @bodhish / @gigincg

@rahulharpal1603
Copy link
Author

I could be wrong, but from product perspective, I don't see any use case for adding this here. Authenticated users would definitely be inside the facility itself right? This would've added value if it was in the public page where patients get to see the facility details.

cc: @bodhish / @gigincg

I thought from the perspective of the district admin, where he/she can see details about various facilities. In the facilities page for the admin, many facilities were listed instead of only one.

@github-actions github-actions bot added needs-triage question Further information is requested labels Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feat: Add Google Maps link for a facility in its page.
4 participants