Don't assume due dates on sections
The content highlights code assumed due dates existed on all sections. But we recently broke that assumption. So now we recalculate the spread of sections across the expected duration ourselves rather than rely on due dates.
Showing
- openedx/core/djangoapps/course_date_signals/handlers.py 3 additions, 6 deletionsopenedx/core/djangoapps/course_date_signals/handlers.py
- openedx/core/djangoapps/course_date_signals/utils.py 16 additions, 6 deletionsopenedx/core/djangoapps/course_date_signals/utils.py
- openedx/core/djangoapps/schedules/content_highlights.py 22 additions, 13 deletionsopenedx/core/djangoapps/schedules/content_highlights.py
- openedx/core/djangoapps/schedules/resolvers.py 2 additions, 1 deletionopenedx/core/djangoapps/schedules/resolvers.py
- openedx/core/djangoapps/schedules/tests/test_content_highlights.py 7 additions, 5 deletions...ore/djangoapps/schedules/tests/test_content_highlights.py
- openedx/features/course_duration_limits/access.py 4 additions, 0 deletionsopenedx/features/course_duration_limits/access.py
Please register or sign in to comment