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

Fix: Same value can be selected multiple times in Questions Components #10288

Closed

Conversation

AdityaJ2305
Copy link
Contributor

@AdityaJ2305 AdityaJ2305 commented Jan 30, 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

  • Bug Fixes
    • Prevented duplicate entries for allergies, diagnoses, and symptoms in the questionnaire
    • Added validation to ensure unique entries based on their respective codes

Copy link
Contributor

coderabbitai bot commented Jan 30, 2025

Walkthrough

The pull request introduces a consistent approach to preventing duplicate entries across three questionnaire question components: AllergyQuestion, DiagnosisQuestion, and SymptomQuestion. In each component, a new conditional check is added to the respective handleAdd* function to prevent adding items with duplicate codes. This change ensures that users cannot select the same value multiple times within these questionnaire components, addressing a potential user experience and data integrity issue.

Changes

File Change Summary
src/components/Questionnaire/QuestionTypes/AllergyQuestion.tsx Added check to prevent duplicate allergies using allergies.some((a) => a.code.code === code.code)
src/components/Questionnaire/QuestionTypes/DiagnosisQuestion.tsx Added check to prevent duplicate diagnoses using diagnoses.some((d) => d.code.code === code.code)
src/components/Questionnaire/QuestionTypes/SymptomQuestion.tsx Added check to prevent duplicate symptoms using symptoms.some((s) => s.code.code === code.code)

Assessment against linked issues

Objective Addressed Explanation
Prevent duplicate value selection [#10099]

Possibly related PRs

Suggested Labels

needs testing, needs review

Suggested Reviewers

  • rithviknishad
  • Jacobjeevan

Poem

🐰 In the realm of forms so neat,
No duplicates shall we repeat!
Allergies, symptoms, diagnoses clear,
Each entry unique, we hold them dear.
A rabbit's code, precise and bright,
Prevents the clutter, sets things 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 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 30, 2025

Deploy Preview for care-ohc failed.

Name Link
🔨 Latest commit 7c7f51d
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/679b7a662ca18700082b7fcd

@AdityaJ2305 AdityaJ2305 marked this pull request as ready for review January 30, 2025 10:06
@AdityaJ2305 AdityaJ2305 requested a review from a team as a code owner January 30, 2025 10:06
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 (3)
src/components/Questionnaire/QuestionTypes/SymptomQuestion.tsx (1)

313-313: LGTM! Consider adding user feedback for duplicate attempts.

The duplicate prevention logic is clean and efficient. However, it silently returns when a duplicate is found.

Consider showing a toast notification when attempting to add a duplicate symptom to improve user experience:

-    if (symptoms.some((s) => s.code.code === code.code)) return;
+    if (symptoms.some((s) => s.code.code === code.code)) {
+      toast({
+        title: t("duplicate_symptom"),
+        description: t("symptom_already_exists"),
+        variant: "warning",
+      });
+      return;
+    }
src/components/Questionnaire/QuestionTypes/DiagnosisQuestion.tsx (1)

119-119: LGTM! Consider adding user feedback for duplicate attempts.

The duplicate prevention logic is clean and consistent with other components. However, it silently returns when a duplicate is found.

Consider showing a toast notification when attempting to add a duplicate diagnosis to improve user experience:

-    if (diagnoses.some((d) => d.code.code === code.code)) return;
+    if (diagnoses.some((d) => d.code.code === code.code)) {
+      toast({
+        title: t("duplicate_diagnosis"),
+        description: t("diagnosis_already_exists"),
+        variant: "warning",
+      });
+      return;
+    }
src/components/Questionnaire/QuestionTypes/AllergyQuestion.tsx (1)

149-149: LGTM! Consider adding user feedback for duplicate attempts.

The duplicate prevention logic is clean and consistent with other components. However, it silently returns when a duplicate is found.

Consider showing a toast notification when attempting to add a duplicate allergy to improve user experience:

-    if (allergies.some((a) => a.code.code === code.code)) return;
+    if (allergies.some((a) => a.code.code === code.code)) {
+      toast({
+        title: t("duplicate_allergy"),
+        description: t("allergy_already_exists"),
+        variant: "warning",
+      });
+      return;
+    }
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 50cb157 and e6e9967.

📒 Files selected for processing (3)
  • src/components/Questionnaire/QuestionTypes/AllergyQuestion.tsx (1 hunks)
  • src/components/Questionnaire/QuestionTypes/DiagnosisQuestion.tsx (1 hunks)
  • src/components/Questionnaire/QuestionTypes/SymptomQuestion.tsx (1 hunks)
🔇 Additional comments (1)
src/components/Questionnaire/QuestionTypes/AllergyQuestion.tsx (1)

Line range hint 313-313: Verify implementation consistency across components.

The duplicate prevention logic has been consistently implemented across all three components (Symptom, Diagnosis, and Allergy).

Let's verify the consistency of the implementation:

Also applies to: 119-119, 149-149

✅ Verification successful

Implementation consistency verified across components

The duplicate prevention logic is implemented consistently in all three components (Symptom, Allergy, and Diagnosis) using the same pattern and structure.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that all three components implement the same duplicate prevention pattern

# Test: Search for the duplicate prevention pattern in all components
echo "Checking duplicate prevention pattern in all components..."
rg -U 'if \((symptoms|diagnoses|allergies)\.some\(\([a-z]\) => \1\.code\.code === code\.code\)\) return;'

# Test: Ensure no other duplicate prevention patterns exist
echo "Checking for any other duplicate prevention patterns..."
rg -U 'code\.code === code\.code'

Length of output: 1362

@github-actions github-actions bot added the Deploy-Failed Deplyment is not showing preview label Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Deploy-Failed Deplyment is not showing preview
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Same value can be selected multiple times in Questions Components
2 participants