Jetpack Section: Remove Jetpack Feature Flags#14409
Conversation
Since it has been already two weeks after the release of the 'Jetpack Section' project, this feature flag can be now safely removed.
Since it has been already two weeks after the release of the 'Jetpack Section' project, this feature flag can be now safely removed.
Since it has been already two weeks after the release of the 'Jetpack Section' project, this feature flag can be now safely removed.
Since it has been already two weeks after the release of the 'Jetpack Section' project, this feature flag can be now safely removed.
Since it has been already two weeks after the release of the 'Jetpack Section' project, this feature flag can be now safely removed.
Since the restore available feature flag is now removed, this rewind dialog logic becomes unused and as such can be completely removed.
Since the restore available feature flag is now removed, this rewind click listener logic, which is associated with the show more menu, becomes unused and as such can be completely removed.
This field is unused and as such can be now safely removed.
This field is unused and as such can be now safely removed.
This update removes 6 issues.
|
You can trigger optional UI/connected tests for these changes by visiting CircleCI here. |
Generated by 🚫 dangerJS |
|
👋 @leandroalonso ! I want to bring this PR to your attention so as you can give the 🟢 light that we can now get rid of all the PS: 👋 @malinajirka ! It would be great if we got your 👍 as well! 🙏 |
|
You can test the changes on this Pull Request by downloading the APK here. |
malinajirka
left a comment
There was a problem hiding this comment.
Thanks for working on this @ParaskP7! I've scanned through the changes and they look good to me. Having said that I didn't do a full review, let me know if you'd prefer me to do a full review.
| } | ||
|
|
||
| // TODO: Inline this method when legacy MySiteFragment is removed | ||
| public static boolean isScanEnabled(boolean scanFeatureFlagEnabled, boolean scanPurchased, SiteModel site) { |
There was a problem hiding this comment.
❓ I'm wondering if we should wait with removal of this method until MySiteFragment gets replaced with the ImprovedMySiteFragment. Someone might not realize both of these fragment exist and update the condition in just one of them. Wdyt?
There was a problem hiding this comment.
Good point @malinajirka. If you decide to change this @ParaskP7 , I can run through my tests again. Just let me know.
There was a problem hiding this comment.
👋 Jirka!
Yeap, I was thinking about that too, I think it is better for me to revert that change, we already talked about that when that got introduced in the codebase. I just wanted to clean this up as well, but, it is better to be on the safe side for now.
PS: @zwarm , I'll do this tomorrow and let you know. 🙏
There was a problem hiding this comment.
👋 @malinajirka @zwarm !
This is now done here: b7d3385
There was a problem hiding this comment.
Thanks for making the change and it works as expected. 👍
Until the legacy 'MySiteFragment' class is removed, it is better if this utils method is used instead of duplicating the conditions in two separate places.
…id into issue/13267-remove-jetpack-feature-flags
Fixes #13267
This PR is responsible for removing all
Jetpack Sectionrelated feature flags from the codebase. After that, the wholeJetpack Sectiongrandparent related issue (see fixes) can be closed since those are the last items on its todo list.To test:
My Sitetab.Activity LogandBackupscreens and more specifically make sure theActivity Log Filtersare available and functional.Backupscreen individually and more specifically make sure the screen is available and functional.Scanscreen and more specifically make sure the screen is available and functional.Back Downloadscreen and flows from within theActivity LogandBackupscreens.Restorescreen and flows from within theActivity LogandBackupscreens.Merge instructions:
Regression Notes
N/A
N/A
N/A
PR submission checklist:
RELEASE-NOTES.txtif necessary.