-
Notifications
You must be signed in to change notification settings - Fork 434
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 wrong terminology used in place of Log Update #9089
base: develop
Are you sure you want to change the base?
Changes from 11 commits
58cb9ad
59ef537
07c8b86
656847d
5e25f47
bf81756
4437778
d44f5b3
0f3ae99
d60eba5
732e1c8
465274f
2487bd3
e29a2b3
d2a2e05
79a3616
26ed105
eccc86a
8d6edaa
54c6464
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,9 +24,9 @@ export default function ShowPushNotification({ id }: { id: string }) { | |
case "PATIENT_CONSULTATION_UPDATED": | ||
return `/facility/${caused_objects?.facility}/patient/${caused_objects?.patient}/consultation/${caused_objects?.consultation}`; | ||
case "PATIENT_CONSULTATION_UPDATE_CREATED": | ||
return `/facility/${caused_objects?.facility}/patient/${caused_objects?.patient}/consultation/${caused_objects?.consultation}/daily-rounds/${caused_objects?.daily_round}`; | ||
return `/facility/${caused_objects?.facility}/patient/${caused_objects?.patient}/consultation/${caused_objects?.consultation}/log_updates/${caused_objects?.daily_round}`; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Codebase verification The parameter
🔗 Analysis chainConsider updating the parameter name for consistency. While the URL paths have been updated to use - return `/facility/${caused_objects?.facility}/patient/${caused_objects?.patient}/consultation/${caused_objects?.consultation}/log_updates/${caused_objects?.daily_round}`;
+ return `/facility/${caused_objects?.facility}/patient/${caused_objects?.patient}/consultation/${caused_objects?.consultation}/log_updates/${caused_objects?.log_update}`; Let's check if this parameter name is used elsewhere in the codebase: Also applies to: 29-29 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Search for daily_round parameter usage in TypeScript/JavaScript files
rg -t ts -t tsx -t js "daily_round" -A 3 -B 3
Length of output: 73 Script: #!/bin/bash
# Search for daily_round parameter usage in TypeScript/JavaScript files
rg -t ts -t typescriptreact -t js "daily_round" -A 3 -B 3
Length of output: 97 Script: #!/bin/bash
# Search for daily_round parameter usage in TypeScript/JavaScript files
rg -g "*.ts" -g "*.tsx" -g "*.js" "daily_round" -A 3 -B 3
Length of output: 15086 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We still call the backend model as DailyRound and not opening an PR as we will soon revamping it according FHIR
Backend api routes
This as well from backend
This is removed as a plug.
This as well related to Model.
Left out is the model field coming from backend @rithviknishad what do you think ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
case "PATIENT_CONSULTATION_UPDATE_UPDATED": | ||
return `/facility/${caused_objects?.facility}/patient/${caused_objects?.patient}/consultation/${caused_objects?.consultation}/daily-rounds/${caused_objects?.daily_round}`; | ||
return `/facility/${caused_objects?.facility}/patient/${caused_objects?.patient}/consultation/${caused_objects?.consultation}/log_updates/${caused_objects?.daily_round}`; | ||
case "INVESTIGATION_SESSION_CREATED": | ||
return `/facility/${caused_objects?.facility}/patient/${caused_objects?.patient}/consultation/${caused_objects?.consultation}/investigation/${caused_objects?.session}`; | ||
case "PATIENT_NOTE_ADDED": | ||
|
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.
💡 Codebase verification
Remaining instances of "Consultation Update" found.
Please update the following files to ensure terminology consistency:
src/components/Facility/ConsultationCard.tsx
src/common/constants.tsx
cypress/pageobject/Patient/PatientConsultation.ts
cypress/e2e/patient_spec/PatientLogUpdate.cy.ts
cypress/e2e/patient_spec/PatientConsultationCreation.cy.ts
🔗 Analysis chain
LGTM! The terminology changes align with the PR objectives.
The text changes from "Patient Consultation Update" to "Patient Log Update" are consistent with the broader effort to standardize terminology across the application.
Let's verify that this terminology change is consistently applied across the codebase:
Also applies to: 661-661
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 383
Script:
Length of output: 2033
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.
@coderabbitai Addressed in 79a3616, d2a2e05
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.
@yash-learner, thanks for addressing the previous feedback with your recent commits. However, I have found that there are still some remaining instances of "Consultation Update" in the codebase. Specifically, the phrase appears in the following files:
src/common/constants.tsx
:text: "Patient Consultation Updated",
cypress/e2e/patient_spec/PatientLogUpdate.cy.ts
:cy.verifyNotification("Consultation updated successfully");
cypress/e2e/patient_spec/PatientConsultationCreation.cy.ts
:cy.verifyNotification("Consultation updated successfully");
Could you please update these instances to "Log Update" to ensure consistent terminology throughout the application?
🔗 Analysis chain
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 576