Skip to content

Jetpack Section: Remove Jetpack Feature Flags#14409

Merged
zwarm merged 14 commits intodevelopfrom
issue/13267-remove-jetpack-feature-flags
Apr 7, 2021
Merged

Jetpack Section: Remove Jetpack Feature Flags#14409
zwarm merged 14 commits intodevelopfrom
issue/13267-remove-jetpack-feature-flags

Conversation

@ParaskP7
Copy link
Copy Markdown
Contributor

@ParaskP7 ParaskP7 commented Apr 6, 2021

Fixes #13267

This PR is responsible for removing all Jetpack Section related feature flags from the codebase. After that, the whole Jetpack Section grandparent related issue (see fixes) can be closed since those are the last items on its todo list.

To test:

  • Launch the app and go to My Site tab.
  • Test the Activity Log and Backup screens and more specifically make sure the Activity Log Filters are available and functional.
  • Test the Backup screen individually and more specifically make sure the screen is available and functional.
  • Test the Scan screen and more specifically make sure the screen is available and functional.
  • Test the Back Download screen and flows from within the Activity Log and Backup screens.
  • Test the Restore screen and flows from within the Activity Log and Backup screens.

Merge instructions:

Regression Notes

  1. Potential unintended areas of impact

N/A

  1. What I did to test those areas of impact (or what existing automated tests I relied on)

N/A

  1. What automated tests I added (or what prevented me from doing so)

N/A

PR submission checklist:

  • I have completed the Regression Notes.
  • I have considered adding accessibility improvements for my changes.
  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

ParaskP7 added 12 commits April 6, 2021 12:39
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.
@ParaskP7 ParaskP7 added this to the 17.2 milestone Apr 6, 2021
@ParaskP7 ParaskP7 requested a review from zwarm April 6, 2021 12:50
@ParaskP7 ParaskP7 self-assigned this Apr 6, 2021
@peril-wordpress-mobile
Copy link
Copy Markdown

peril-wordpress-mobile bot commented Apr 6, 2021

You can trigger optional UI/connected tests for these changes by visiting CircleCI here.

@peril-wordpress-mobile
Copy link
Copy Markdown

Warnings
⚠️ PR has more than 500 lines of code changing. Consider splitting into smaller PRs if possible.

Generated by 🚫 dangerJS

@ParaskP7
Copy link
Copy Markdown
Contributor Author

ParaskP7 commented Apr 6, 2021

👋 @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 Jetpack Section related feature flags from our codebase. It has been some time since we release and it seems that now it is a good time to remove those. Wdyt?

PS: 👋 @malinajirka ! It would be great if we got your 👍 as well! 🙏

@peril-wordpress-mobile
Copy link
Copy Markdown

peril-wordpress-mobile bot commented Apr 6, 2021

You can test the changes on this Pull Request by downloading the APK here.

@zwarm zwarm self-assigned this Apr 6, 2021
Copy link
Copy Markdown
Contributor

@malinajirka malinajirka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❓ 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?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point @malinajirka. If you decide to change this @ParaskP7 , I can run through my tests again. Just let me know.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👋 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. 🙏

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👋 @malinajirka @zwarm !

This is now done here: b7d3385

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for making the change and it works as expected. 👍

Copy link
Copy Markdown
Contributor

@zwarm zwarm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ParaskP7 - All looks good. I tested the the Jetpack features including on the my_site_improvements_enabled flag. Thanks for the cleanup too!

Feel free to merge once you get the 👍 .

@leandroalonso
Copy link
Copy Markdown
Contributor

@ParaskP7 🟢 :shipit:

ParaskP7 added 2 commits April 7, 2021 10:51
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
@zwarm zwarm merged commit 2868476 into develop Apr 7, 2021
@zwarm zwarm deleted the issue/13267-remove-jetpack-feature-flags branch April 7, 2021 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Jetpack Section: Project Issue

4 participants