-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Open
Labels
c.BreakingFeature deprecation/removal or other changes that significantly breaks existing user flowFeature deprecation/removal or other changes that significantly breaks existing user flow
Description
Problem Statement
The "archive courses" function was introduced when all courses are loaded in instructor's home page without any lazy loading, in order to reduce both the backend load and the page load time (and those are pre-V7 time where backend and page load are essentially the same thing).
However, not only that we now have lazy loading, but also the data for courses, no matter how large, are fetched asynchronously (REST architecture).
- Unless the scale is in hundreds of thousands of courses, loading all courses (skeletons) for any user will not put any significant load to the backend.
- The bottleneck is in fact the frontend who unfortunately have to "display" those large number of courses.
- Even if the above (number of courses causing page to be cluttered) does happen, "archiving courses" is not the proper solution because it assumes that some courses are "less active" than the others. The only true solution is applying pagination.
Right now, "archive courses" is no longer justifiable to be kept around.
Solution
- Remove the feature entirely
- (lower priority) Introduce pagination for courses in the instructor home page and/or instructor courses page and/or instructor students list page
Metadata
Metadata
Assignees
Labels
c.BreakingFeature deprecation/removal or other changes that significantly breaks existing user flowFeature deprecation/removal or other changes that significantly breaks existing user flow