-
Notifications
You must be signed in to change notification settings - Fork 51
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
Update Django to 3.2 #1323
Update Django to 3.2 #1323
Conversation
…rror from 28 to 11 according to test unit
Woohooooo!! Thank you @kewlguy781 !!! Requesting some review of the Decimal and AutoField changes from @Jkrzy pretty please. I'm super-excited to get this merged... ❤️ |
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.
This looks great! There's one small opportunity I noted to align requirements.txt
with the lock file
Codecov Report
@@ Coverage Diff @@
## main #1323 +/- ##
==========================================
+ Coverage 88.61% 88.63% +0.02%
==========================================
Files 51 51
Lines 2222 2226 +4
==========================================
+ Hits 1969 1973 +4
Misses 253 253
Continue to review full report at Codecov.
|
Description
This PR will update the Django web application to 3.2 (which is the next LTS release)
Additional information
Changes done to work with Django 3.2:
billable = Coalesce(Sum('timecardobjects__hours_spent', filter=billable_filter), 0)
->billable = Coalesce(Sum('timecardobjects__hours_spent', filter=billable_filter), Decimal('0'))
The former code set the variable as integer 0, while the rest is in Decimal. We changed it to Decimal to play nice with other variables that are already in Decimal. See Value() Changes under ModelAutoField
instead of new defaultBigAutoField
however, we will need to revisit this and migrate into database.cg-django-uaa
to support Django 3.2 (Special shout out to @bengerman13 for working with me)