feat: removes sidebar upgrade notification component#1410
feat: removes sidebar upgrade notification component#1410zacharis278 wants to merge 4 commits intomasterfrom
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1410 +/- ##
==========================================
+ Coverage 88.87% 89.02% +0.15%
==========================================
Files 307 306 -1
Lines 5285 5168 -117
Branches 1344 1280 -64
==========================================
- Hits 4697 4601 -96
+ Misses 572 551 -21
Partials 16 16 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| courseId, | ||
| }} | ||
| > | ||
| <LockPaywall courseId={courseId} /> |
There was a problem hiding this comment.
I had this removed originally but after thinking it through my instinct is we actually don't want to touch this. I'll leave it here for now to discuss.
Is content gating edx.org specific or a core feature of Open edX that should have an associated paywall/view in this MFE?
There was a problem hiding this comment.
My instinct is that this should remain as it feels like a core feature of Open edX, but I'm guessing you're leaving here to confirm with Axim?
| jest.mock('@edx/frontend-platform/analytics'); | ||
|
|
||
| /* eslint-disable react/prop-types */ | ||
| jest.mock('@openedx/frontend-plugin-framework', () => ({ |
There was a problem hiding this comment.
this is the only addition here since there are tests that rely on a close button within the notification that toggle the sidebar. We need a 'mock' notification now since there is no default
|
FYI @arbrandes |
varshamenon4
left a comment
There was a problem hiding this comment.
Looks good! Just added some comments and questions.
| } = useModel('courseHomeMeta', courseId); | ||
|
|
||
| const { | ||
| accessExpiration, |
There was a problem hiding this comment.
The props removed here are just the ones that are no longer being used by the UpgradeNotification, correct?
| <PluginSlot | ||
| id="outline_tab_notifications_slot" | ||
| pluginProps={{ courseId }} | ||
| > |
| @@ -81,24 +74,7 @@ const NotificationsWidget = () => { | |||
| setNotificationCurrentState: setUpgradeNotificationCurrentState, | |||
| toggleSidebar: onToggleSidebar, | |||
| }} | |||
There was a problem hiding this comment.
Suggestion: the notificationCurrentState and setNotificationCurrentState in the PluginSlot pluginProps above can also be removed, correct?
There was a problem hiding this comment.
these are still needed since pluggable notification components use this as a callback to open or close the sidebar
| courseId, | ||
| }} | ||
| > | ||
| <LockPaywall courseId={courseId} /> |
There was a problem hiding this comment.
My instinct is that this should remain as it feels like a core feature of Open edX, but I'm guessing you're leaving here to confirm with Axim?
48309c7 to
397f6a7
Compare
|
@arbrandes as requested this is a follow up to remove unused code as part of openedx/platform-roadmap#332. I'll leave timing of merging this up to Axim since this has already been removed from edx.org |
|
@arbrandes is there still desire to have this removed as part of the 2U work? I'm clearing out this project on our end and this is the only open task. |
|
@zacharis278 @arbrandes I would like to get this merged. Is there anything blocking merging it? An open question about |
|
@jristau1984 Is there someone from TNL who can advise on getting this PR finished? I'd like to get this unused code removed, and I think it just needs a rebase. I'm happy to help but don't have as much context on what's still needed or not. CC @arbrandes |
|
Thanks for the pull request, @zacharis278! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Submit a signed contributor agreement (CLA)
If you've signed an agreement in the past, you may need to re-sign. Once you've signed the CLA, please allow 1 business day for it to be processed. 🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
|
Hey @zacharis278, the CLA check for this PR is failing so it looks like you'll need to go back and follow the instructions from the bot about submitting a signed CLA. |
|
@nsprenkle and @jansenk are 2U learning MFE folks. |
|
@itsjeyd thanks I'm no longer with 2U or contributing to the project. This kinda just got left over, happy to close the PR if the branch isn't useful anymore otherwise someone else will need to pick this up. |
|
Ported over to #1675. |
Followup to #1368.
These components are specific to edx.org and will be moved to a 2U owned plugin. There are some open questions and I'd like to go back and manually test everything once the 2U plugin is updated to no longer import these. Leaving this in draft state for now.edx.org has migrated these components to a 2U owned plugin. This code is no longer being used and can be deprecated. While the LockPaywall is also unused we have opted not to remove it as originally intended. See note below
Removed by this PR
LockPaywall: Upgrade ad shown in place of graded unit if content gating is enabledNo longer included in this PRUpsellBullets: Only used by Upgrade/PaywallCannot be removed since we're keeping the LockPaywallNot Removed by this PR
Open Questions
Unsure on what to do with the LockPaywall. Should this actually be removed? It puts us in a weird state where 'nothing' would be displayed if content gating is enabled and that plugin slot isn't configured. I'm thinking this should either be reworked so the
shouldDisplayContentGatinglogic moves into the plugin itself or we don't touch LockPaywall at all here.Decision: We will not be removing the LockPaywall as part of this effort