-
Notifications
You must be signed in to change notification settings - Fork 1
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
Remove Cohort
model
#2784
Draft
thomasleese
wants to merge
3
commits into
replace-cohort-with-organisation
Choose a base branch
from
remove-cohorts
base: replace-cohort-with-organisation
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Remove Cohort
model
#2784
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
thomasleese
added
📐 data_consistency
Validations and data tweaks
🛠️ refactor
Improving maintainability
labels
Dec 19, 2024
thomasleese
force-pushed
the
remove-cohorts
branch
from
December 19, 2024 16:48
fc5b9af
to
9c151dd
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
December 20, 2024 11:28
08af78b
to
e9533b0
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
December 20, 2024 11:28
9c151dd
to
40e565f
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
December 20, 2024 14:35
e9533b0
to
f76bbf6
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
December 20, 2024 14:36
40e565f
to
86c1d16
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 5, 2025 10:58
86c1d16
to
03c7835
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
January 5, 2025 10:59
f76bbf6
to
e0ed571
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 7, 2025 13:44
03c7835
to
020eaf6
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
2 times, most recently
from
January 7, 2025 13:49
2b320bd
to
e8dfb1b
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
2 times, most recently
from
January 8, 2025 11:30
792a42e
to
4336c91
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
2 times, most recently
from
January 8, 2025 13:51
e75047f
to
cd002d6
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 8, 2025 13:54
4336c91
to
4ec3e9e
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
January 8, 2025 14:37
cd002d6
to
bc17344
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 8, 2025 14:37
4ec3e9e
to
c397b67
Compare
thomasleese
added a commit
that referenced
this pull request
Jan 8, 2025
This fixes a few minor visual issues spotted by the testers when testing #2780 where if the date of birth is missing the same error will appear twice for each row, and similarly an issue where the year group wouldn't render correctly. This fixes are already in place for a future release (in #2783 and #2784), however including them now makes the testing easier and avoids needing to record additional defects.
thomasleese
added a commit
that referenced
this pull request
Jan 8, 2025
This fixes a few minor visual issues spotted by the testers when testing #2780 where if the date of birth is missing the same error will appear twice for each row, and similarly an issue where the year group wouldn't render correctly. This fixes are already in place for a future release (in #2783 and #2784), however including them now makes the testing easier and avoids needing to record additional defects.
thomasleese
added a commit
that referenced
this pull request
Jan 8, 2025
This fixes a few minor visual issues spotted by the testers when testing #2780 where if the date of birth is missing the same error will appear twice for each row, and similarly an issue where the year group wouldn't render correctly. This fixes are already in place for a future release (in #2783 and #2784), however including them now makes the testing easier and avoids needing to record additional defects. ## Screenshots ![{CFD5D2F8-A8E7-40F1-B323-45361B94AB3A}](https://github.com/user-attachments/assets/fa2a0a2b-9ad0-4913-a71f-ea48ae7c82cf) ![{9A759A33-DF06-4FCC-9F59-9B9C8FF22271}](https://github.com/user-attachments/assets/eef016c9-47ad-4b14-8ced-5e2dd8e19427)
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
January 9, 2025 08:55
bc17344
to
91a9062
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 9, 2025 08:55
c397b67
to
7cbd7af
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 10, 2025 11:45
7cbd7af
to
eca7249
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
January 10, 2025 11:45
91a9062
to
7b7939f
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
2 times, most recently
from
January 13, 2025 16:58
d5304a1
to
ecd27b0
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 13, 2025 16:59
eca7249
to
1316e6d
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
January 13, 2025 17:08
ecd27b0
to
42701d1
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 13, 2025 17:08
1316e6d
to
4aed646
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
January 13, 2025 17:29
42701d1
to
500e67b
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 13, 2025 17:29
4aed646
to
e2ea0bc
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
January 14, 2025 17:22
500e67b
to
91c7d09
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 14, 2025 17:22
e2ea0bc
to
1fdd6a5
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
January 15, 2025 10:49
91c7d09
to
a8b8972
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 15, 2025 10:49
1fdd6a5
to
db63555
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 15, 2025 16:19
db63555
to
7e6f78a
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
January 16, 2025 08:34
a8b8972
to
b3b43de
Compare
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 16, 2025 08:34
7e6f78a
to
9372fa6
Compare
thomasleese
force-pushed
the
replace-cohort-with-organisation
branch
from
January 17, 2025 16:34
b3b43de
to
4488ee2
Compare
This removes the table and the reference on the patient model as we no longer need cohorts and they're not used anywhere.
This removes the `Cohort` model and related code which is no longer used.
This removes the concern as it's only beind used by one model now.
thomasleese
force-pushed
the
remove-cohorts
branch
from
January 17, 2025 16:34
9372fa6
to
4adda65
Compare
Quality Gate passedIssues Measures |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
In #2783 we've replaced the usage of the
Cohort
model with a directly foreign key relationship to the organisation. This means the model can be safely removed as it was no longer being used.