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.

Sign up for GitHub

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

Jump to bottom

Set current_bed to None when discharging and custom migration for past consultations. #1401

Merged
merged 3 commits into from
Jun 22, 2023
Merged

Set current_bed to None when discharging and custom migration for past consultations. #1401

merged 3 commits into from
Jun 22, 2023

Conversation

rithviknishad
Copy link
Member

Proposed Changes

  • When consultation is discharged, set current_bed to None
  • Custom migration: Set current_bed to None for existing consultations where there's no discharge data and current bed is not None.

Associated Issue

Merge Checklist

  • Tests added/fixed
  • Update docs in /docs
  • Linting Complete
  • Any other necessary step

Only PR's with test cases included and passing lint and test pipelines will be reviewed

@coronasafe/care-backend-maintainers @coronasafe/care-backend-admins

@vigneshhari vigneshhari merged commit 4260241 into master Jun 22, 2023
5 checks passed
@vigneshhari vigneshhari deleted the fix#1400 branch June 22, 2023 07:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@vigneshhari vigneshhari vigneshhari approved these changes

@sainak sainak Awaiting requested review from sainak

Assignees
No one assigned
Labels
waiting-for-review
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

current_bed is not set to None when consultation is discharged
2 participants
@rithviknishad @vigneshhari