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
When you go to a course outline, open network tab in the Developer console you will see a request like this /api/contentstore/v1/home/courses which fetches all courses in one instance.
I don't know if this data is being used for anything, but even if it is, it is still a major performance issue.
The code and the file are below: useEffect(() => { dispatch(fetchStudioHomeData()); }, []);
Loading the data via React Query rather than redux actions would make it cached and solve this problem.
Though I also find the idea of a "studio home" API to be a bit of an anti-pattern. It's obviously used to fetch data on other pages besides home, and these days its considered best practice to split into smaller API requests rather than one big one that likely loads more data than you need. I'm not sure whether putting it all into one studio home API was for optimization purposes or what but it does seem unusual.
When you go to a course outline, open network tab in the Developer console you will see a request like this /api/contentstore/v1/home/courses which fetches all courses in one instance.
I don't know if this data is being used for anything, but even if it is, it is still a major performance issue.
The code and the file are below:
useEffect(() => { dispatch(fetchStudioHomeData()); }, []);
https://github.com/openedx/frontend-app-authoring/blob/master/src/CourseAuthoringPage.jsx
The text was updated successfully, but these errors were encountered: