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 contact tracing from event model #3559
Conversation
0499a3e
to
32a6be8
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3559 +/- ##
==========================================
- Coverage 88.24% 88.24% -0.01%
==========================================
Files 669 670 +1
Lines 21118 21089 -29
==========================================
- Hits 18636 18609 -27
+ Misses 2482 2480 -2 ☔ View full report in Codecov by Sentry. |
Resolves ABA-183 |
What is the purpose of the Migrate event you created? |
Absolutely love that you looked through it and asked a question! Extreme kudos for that 💯 I'll add a lil answer as im here anyways - but if anyone has anything to add feel free:) and let me know if I missed what you were actually asking about Quick backstory; In Django we have Whats happening here; In our In this specific case - we wouldn't really break anything by leaving the field there, as it had a default value of False - so if we kept it we would just continue to save a False value for every event created. But in a lot of cases the value might be required - and in that case it wouldn't be possible to create new events if the field wasn't also deleted from the database. And there's literally no reason not to remove it since it's not used Neat stuffs about migrations; We have also setup tests to make sure that the appropriate migrations are created, so if you tried to make changes to the models and did not create the required migrations it would not pass CI:) Another cool thing about migrations is that no matter what version of the code you are running (either on some prod server or locally), the database stores which migrations you have already applied - so when there are new ones you only have to run the ones that you're missing 🚀 This became a tad longer than I planned - but I hope it's not too much and that it's useful(: |
Thanks for the comprehensive answer! |
Remove contact tracing from event model
This PR removes the contact tracing model and views. Depends on webkom/lego-webapp#4476