You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I was working on this #2359 I looked through the catalog course card and it looked like the first relevant run for which we show info is not similar to the logic we use for picking first relevant run for the product page.
The text was updated successfully, but these errors were encountered:
So for the catalog (Course.first_unexpired_run):
we pick the earliest starting or started course run that is enrollable (non-archived preferred).
In the Course product page we are picking the run with the start date that is closest to now (if course.next_run_id is null).
Could not explain why we have getFirstRelevantRun calculation in the front end, if we are already passing next_run_id in the courses api. This is probably ready for some refactoring.
As I was working on this #2359 I looked through the catalog course card and it looked like the first relevant run for which we show info is not similar to the logic we use for picking first relevant run for the product page.
The text was updated successfully, but these errors were encountered: