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

Fixed the facility redirection in organisation #10328

Merged
merged 1 commit into from
Jan 31, 2025

Conversation

nihal467
Copy link
Member

@nihal467 nihal467 commented Jan 31, 2025

Proposed Changes

@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

Summary by CodeRabbit

  • Navigation Update
    • Modified facility detail page link to redirect to facility settings page instead of overview page.

@nihal467 nihal467 requested a review from a team as a code owner January 31, 2025 04:12
Copy link
Contributor

coderabbitai bot commented Jan 31, 2025

Walkthrough

The pull request involves a modification to the navigation path in the OrganizationFacilities component. Specifically, the Link component's href attribute has been updated to change the destination URL for facility details. The change redirects users from an overview page to a general settings page when interacting with a facility within the organization's interface.

Changes

File Change Summary
src/pages/Organization/OrganizationFacilities.tsx Modified Link component's href from /facility/${facility.id}/overview to /facility/${facility.id}/settings/general

Possibly related PRs

Suggested labels

changes required, needs review

Suggested reviewers

  • rithviknishad

Poem

🐰 A rabbit's routing tale unfolds,
Where links and paths their secrets hold
From overview to settings bright,
A navigation journey's slight
Hop along the digital trail! 🌟


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 31, 2025

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit 319cbb9
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/679c4d9f53e2d7000853561d
😎 Deploy Preview https://deploy-preview-10328--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.

Copy link

Deploying care-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: 319cbb9
Status: ✅  Deploy successful!
Preview URL: https://6e07207a.care-fe.pages.dev
Branch Preview URL: https://facility-redirection.care-fe.pages.dev

View logs

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: 0

🧹 Nitpick comments (1)
src/pages/Organization/OrganizationFacilities.tsx (1)

159-159: Add a comment explaining the redirection change.

Consider adding a code comment explaining why users are being redirected to the settings page instead of the overview page. This will help other developers understand the intent behind this change.

                      <Link
+                       {/* Redirecting to settings/general instead of overview as per ISSUE-XXX */}
                        href={`/facility/${facility.id}/settings/general`}
                        className="text-sm w-full hover:underline"
                      >
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fd9f145 and 319cbb9.

📒 Files selected for processing (1)
  • src/pages/Organization/OrganizationFacilities.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: cypress-run (1)
🔇 Additional comments (1)
src/pages/Organization/OrganizationFacilities.tsx (1)

159-159: Verify that the new route exists and is accessible.

The redirection has been changed from overview to settings/general page. While the change looks good, we should verify that this route exists and is properly configured.

Let's verify the route configuration:

✅ Verification successful

The route change is properly configured and valid

The new path /facility/${facility.id}/settings/general is handled by the wildcard route in FacilityRoutes.tsx. The different landing pages (settings vs overview) from different entry points appear to be an intentional UX pattern based on the context of use.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the new route path exists in the router configuration
# and if there are any other components still using the old path

# Search for route definitions
echo "Checking route definitions..."
rg -A 5 "facility/.*settings/general"

# Search for any remaining references to the old path
echo "Checking for old path usage..."
rg -A 5 "facility/.*overview"

Length of output: 2666


Script:

#!/bin/bash
# Search for any settings-related routes in the facility context
echo "Checking facility settings routes..."
rg "facility.*settings" src/Routers/

# Search for the FacilitySettings component
echo "Checking for FacilitySettings component..."
fd -e tsx -e ts "FacilitySettings"

Length of output: 348


Script:

#!/bin/bash
# Check the implementation of the settings route
echo "Checking settings route implementation..."
rg -A 10 "facility/:facilityId/settings\*" src/Routers/routes/FacilityRoutes.tsx

Length of output: 321

Copy link

cypress bot commented Jan 31, 2025

CARE    Run #4514

Run Properties:  status check passed Passed #4514  •  git commit 319cbb98b7: Fixed the facility redirection in organisation
Project CARE
Branch Review facility-redirection
Run status status check passed Passed #4514
Run duration 05m 50s
Commit git commit 319cbb98b7: Fixed the facility redirection in organisation
Committer Mohammed Nihal
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 10
View all changes introduced in this branch ↗︎

@rithviknishad rithviknishad merged commit 34c7b68 into develop Jan 31, 2025
30 of 33 checks passed
@rithviknishad rithviknishad deleted the facility-redirection branch January 31, 2025 05:21
Copy link

@nihal467 Your efforts have helped advance digital healthcare and TeleICU systems. 🚀 Thank you for taking the time out to make CARE better. We hope you continue to innovate and contribute; your impact is immense! 🙌

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.

Fix the redirection of users to Facility Details Page Via Organization
2 participants