-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DEPR]: Upgrade Button #438
Comments
@jsnwesson hello! Is there an associated ticket for this work/which squad is removing it? Purchase squad uses this Upgrade Button and we were not aware of the removal |
Hi @julianajlk ! This work is to be done by my team (Aperture). To be clear, we'll actually be keeping the Upgrade button for 2U, but it will be stored as a plugin and preserved in frontend-plugin-learner-dashboard. It is intended to work exactly as before, but the benefit is that this button doesn't exist out-of-the-box for Learner Dashboard. |
@jsnwesson Great, I misunderstood and assumed we'd need to make changes on our end to accommodate for this change. If you need any testing to be done when this goes out to production, please let us know. Thank you! |
@jsnwesson is this work done now? I saw that #464 has merged, is there anything else left for this DEPR? |
@feanil there is some work that still needs to be done for this, which involves creating a private plugin that will live in a private 2U-owned repo. Once that's done, we can remove the upgrade button code from the Learner Dashboard repo. |
@jsnwesson, can you give us an update on when the upgrade button will be removed? |
Hi @arbrandes ! @MaxFrank13 is working on creating the upgrade button plugin this week. Once it's in working order, we hope to be able to immediately remove the upgrade button code from Learner Dashboard! |
This removes the upgrade button as default content in CourseCardActionSlot. This is, for the moment, a Sumac-specific change. The button is still present in master, pending proper removal (including the component definitions from the rest of the repository) prior to the U release by the maintainers. See: openedx#438
This removes the upgrade button as default content in CourseCardActionSlot. This is, for the moment, a Sumac-specific change. The button is still present in master, pending proper removal (including the component definitions from the rest of the repository) prior to the U release by the maintainers. See: #438
Proposal Date
2024-08-27
Target Ticket Acceptance Date
2024-09-10
Earliest Open edX Named Release Without This Functionality
Sumac - 2024-10
Rationale
The Upgrade Button has been the most commonly requested component by the Open edX community for removal. As far as we can tell, 2U is the only organization that uses the component, which is why a complete removal of the button is the proposed approach as opposed to making it an optional component that can be injected within a PluginSlot. If the code is indeed unused, it only serves as a liability to the community and should be removed.
Removal
This is a proposal to remove the Upgrade Button component, its implementation in CourseCardActions, and any hooks logic and tracking events that are only related to "upgrading" a course.
For the sake of removing the Upgrade Button before the Sumac release, this deprecation proposal doesn't include completely removing upgrade-related information from the
LearnerDashboard.Init()
call to the LMS, which also means that the remaining evidence within Learner Dashboard of a course ever being upgradeable would be found in a redux selector. If this were to remain, then it would at least give the Maintaining team the time to remove the Upgrade data from theinit
, as any need to call LearnerDashboard.Init() more than once will have a tremendous impact on the performance of the page.Replacement
With these removals, in CourseCardActions there would be an empty PluginSlot in place of where the Upgrade Component was implemented to allow for the component to be plugged in using Frontend Plugin Framework. This would also allow any other organization to add whatever action components they would like.
Deprecation
No response
Migration
No response
Additional Info
@jsnwesson
Discourse Post
Task List
The text was updated successfully, but these errors were encountered: