Rutvik Solanki

The model connection between Course and Trainings has now been updated to a one-to-many relationship. The initial plan of implementing the M2M was to avoid adding new fields to training....

@tompollard @bemoody When a user is taking a course, we only add a training in the system at the end of the course. The training directly gets to the Accepted...

@tompollard @bemoody I've tried summarizing the larger goal & the smaller chunks the entire Course functionality was broken into #2299 This is the third part of the functionality required to...

Addressing the comments by @tompollard 1. Added a Check in course creation workflow, ensuring that two course with same name can not be added. Check for appropriate versions have already...

@bemoody I've updated the URL for the heading and the PR is ready for further review / merge.

@bemoody I've implemented the updates. I agree with you on the fact that the whole page would need updating. currently, there is hardcoded behavior to show a particular template info...

Heyy @bemoody Thanks for the detailed review and I really appreciate your thoughtful comments! I'll keep these points in mind while writing queries now onwards.

@bemoody Thanks for your review! I did see there were a few loose ends in the way views and routing was managed. Furthermore as you pointed out, there were logical...

> Location of the "update" button in the console Versions of a course are immutable by design (a course version that has been published and taken by users are certified...

@tompollard I've made the changes you requested on switching from expiring to archiving and simplifying the logic. However, there is a weird issue I am facing in the tests. The...