Data Migration to Support New Discharge Reason Field #1773
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1773 +/- ##
=======================================
Coverage 61.04% 61.05%
=======================================
Files 208 208
Lines 11526 11528 +2
Branches 1656 1656
=======================================
+ Hits 7036 7038 +2
Misses 4218 4218
Partials 272 272 ☔ View full report in Codecov by Sentry. |
|
@rithviknishad @sainak @vigneshhari could you review this PR once? |
sainak
added
discussion
waiting-for-review
and removed
waiting-for-review
discussion
labels
sainak
requested changes
Dec 27, 2023
Co-authored-by: Aakash Singh <mail@singhaakash.dev>
Co-authored-by: Aakash Singh <mail@singhaakash.dev>
sainak
approved these changes
Dec 27, 2023
rithviknishad
approved these changes
Dec 30, 2023
|
@vigneshhari could you review this? |
vigneshhari
approved these changes
Jan 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
This PR includes changes for migrating existing data to align with the newly introduced
new_discharge_reasonfield in our database schema. The update ensures backward compatibility and seamless integration of the new field across various modules. The modifications are primarily focused on serializers, viewsets, and tests, ensuring that all functionalities related to patient discharge reasons are updated to use the new field. This change is pivotal for enhancing our data handling capabilities and providing more detailed reasons for patient discharge in our system.Associated Issue
discharge_reasontoIntegerField#1739Phases for the change
@coronasafe/care-backend-maintainers @coronasafe/care-backend-admins