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
Earliest Open edX Named Release Without This Functionality
Teak - 2025-04
Rationale
The HomePageCourses API v1 will be replaced by v2, which offers improvements including pagination, filtering, and sorting. As of Sumac, v2 is the default API used to query the course listing from Studio.
Removal
To completely remove the API v1 in edx-platform it’s necessary:
Removing v1 from the authoring MFE ASAP makes sense. On the platform side, I'm just wondering if we need to mark it as deprecated in Teak and then remove it in the next release, to give API consumers more time to adjust.
Thanks for your comment @bradenmacdonald. Yeah, I think it's better to mark the code as deprecated for Teak, and finally, in Ulmo remove it. I can update the proposal, what do you think? @mariajgrimaldi@feanil
Proposal Date
2025-01-28
Target Ticket Acceptance Date
2025-02-11
Earliest Open edX Named Release Without This Functionality
Teak - 2025-04
Rationale
The
HomePageCourses
API v1 will be replaced by v2, which offers improvements including pagination, filtering, and sorting. As of Sumac, v2 is the default API used to query the course listing from Studio.Removal
To completely remove the API v1 in
edx-platform
it’s necessary:Also, it's necessary to remove all references to API v1 in the Authoring MFE. This work is in progress:
Replacement
API v2 completely replaces API v1. The PRs related to functionality are as follows:
Deprecation
No response
Migration
No response
Additional Info
No response
Task List
edx-platform
frontend-app-authoring
(WIP)The text was updated successfully, but these errors were encountered: