-
Notifications
You must be signed in to change notification settings - Fork 625
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
Show hyphen when no severity in SymptomTable #10662
Show hyphen when no severity in SymptomTable #10662
Conversation
""" WalkthroughThis pull request updates the Changes
Sequence Diagram(s)sequenceDiagram
participant SymptomTable as Component
participant UI as UserInterface
SymptomTable->>SymptomTable: Check if symptom.severity exists?
alt Severity exists
SymptomTable->>UI: Render severity badge
else Severity missing
SymptomTable->>UI: Render "-" as placeholder
end
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for care-ohc ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
…rity-nullity-check
…om/rajku-dev/care_fe into issue/10660/severity-nullity-check
There was a problem hiding this 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/components/Patient/symptoms/SymptomTable.tsx (1)
81-81
: LGTM! The implementation correctly handles empty severity cases.The change aligns with the PR objective and follows the existing pattern in the codebase for handling empty values.
Consider using nullish coalescing for better type safety.
For better type safety and to handle both
undefined
andnull
cases explicitly:-{symptom.severity ? t(symptom.severity) : "-"} +{symptom.severity ?? "-"}
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/components/Patient/symptoms/SymptomTable.tsx
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
- GitHub Check: Test
- GitHub Check: CodeQL-Build
- GitHub Check: cypress-run (1)
- GitHub Check: OSSAR-Scan
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rajku-dev wrap the badge in the condition
@rajku-dev 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! 🙌 |
Proposed Changes
@ohcnetwork/care-fe-code-reviewers
Merge Checklist
Summary by CodeRabbit