-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[MBL-853] Create Feature Flag To Hide Creator Dashboard #1827
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1827 +/- ##
==========================================
- Coverage 84.35% 84.35% -0.01%
==========================================
Files 1276 1276
Lines 115436 115457 +21
Branches 30738 30751 +13
==========================================
+ Hits 97381 97395 +14
- Misses 16988 16994 +6
- Partials 1067 1068 +1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks good, functionality working from dashboard to beta flag tools with caching taking precedence.
One thing - and maybe this is just my sense of how I'm reading the flag - can we remove "Hidden" from the naming? It's just the same as the other flags, "Creator Dashboard" - comment below.
ba09cee
to
15f79dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor miss here, easily corrected, but could be caught the first time around.
@@ -40,4 +40,13 @@ final class RemoteConfigFeatureHelpersTests: TestCase { | |||
XCTAssertFalse(featureFacebookLoginInterstitialEnabled()) | |||
} | |||
} | |||
|
|||
func testCreatorDashboardHidden_RemoteConfig_FeatureFlag_False() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Always remember to update the test names to reflect the correct values being tested. In this case we changed creatorDashboardHiddenEnabled
to creatorDashboardEnabled
so the test name should change as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤦
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for minor changes like this it could be helpful to comment it as a suggestion so that we can easily commit directly from the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, that's normally how I'd do it, but I want us to get into the habit of committing all changes once correctly.
So example - You assign a PR to me, it's reviewed, all changes requested in review, you make as many commits/ask as many questions as you want, but once it's re-assigned back to me, it should pretty much be perfect.
The intention is to reduce the amount of back and forth, just as learning tool. I'm going to explicitly request changes for minor corrections from now on so we get into the habit.
15f79dc
to
8c1f7c9
Compare
📲 What
Create a new feature flag that will allow KS to hide creator tools on iOS in a more controlled way.
This feature flag will be defaulted to
true
because the feature being implemented here is the removal of our creator dashboard.🤔 Why
Creator tools will eventually be removed from the app altogether and this flag will allow us to slowly roll this out.
🛠 How
creator_dashboard
, in our Firebase Remote Config DashboardRemoteConfigFeature
use the same parameter string to add a new enum caseRemoteConfigFeature+Helpers
RemoteConfigFeatureHelpersTests
RemoteConfigFeatureFlagToolsViewControllerTests
and its corresponding snapshot.👀 See
Trello, screenshots, external resources?
✅ Acceptance criteria
You’ll need to run the app locally using the AppCenter Beta scheme.
Remember that Firebase is only configured
#if RELEASE || APPCENTER
creator_dashboard
has been added to the firebase dashboard to the production and beta projects and is defaulted totrue