Skip to content

Implement feature flag enrolment API #6177

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

Merged
merged 7 commits into from
Jun 11, 2025
Merged

Conversation

aitorvs
Copy link
Collaborator

@aitorvs aitorvs commented Jun 4, 2025

Task/Issue URL: https://app.asana.com/1/137249556945/project/1198194956794324/task/1210415399293026?focus=true

Description

Implement the enrolment API as defined in API Proposal: feature flag enrolment API

Steps to test this PR

We tested the following experiments

  • sense of protection
  • app-tp blocklist interceptor
  • default browser prompt
  • blocklist interceptor

Thanks @marcosholgado, @mikescamell , @anikiki , @LukasPaczos

Copy link
Collaborator Author

aitorvs commented Jun 4, 2025

This stack of pull requests is managed by Graphite. Learn more about stacking.

@aitorvs aitorvs force-pushed the feature/aitor/ff/enrollment branch 3 times, most recently from bc9137e to 8698ba0 Compare June 4, 2025 07:33
@@ -55,13 +55,13 @@ class ReactivateUsersExperimentImpl @Inject constructor(
) : ReactivateUsersExperiment {

override suspend fun isControl(): Boolean =
reactivateUsersToggles.reactivateUsersExperimentMay25().isEnabled(CONTROL)
reactivateUsersToggles.reactivateUsersExperimentMay25().isEnrolledAndEnabled(CONTROL)
Copy link
Contributor

Choose a reason for hiding this comment

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

This experiment is missing enrolling users too, I think we can do it in the evaluate method of RealDaxPrompts right after checking the user is eligible (line 55)? cc @anikiki to double check.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, that's correct 👍

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@marcosholgado @anikiki can you check the latest commit to see if that's what we want?

Copy link
Contributor

Choose a reason for hiding this comment

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

I checked and it's what we want 👍

@LukasPaczos
Copy link
Contributor

@aitorvs I pushed a commit that fixes the DefaultBrowserPromptsExperimentImpl unit tests, fortunately only minor tweaks were needed to make it green.

@aitorvs aitorvs force-pushed the feature/aitor/ff/enrollment branch from 5d7fb7b to 5cd6e2b Compare June 6, 2025 15:23
@aitorvs aitorvs force-pushed the feature/aitor/ff/enrollment branch from 3df3c69 to d6eb4b7 Compare June 10, 2025 16:12
@aitorvs aitorvs force-pushed the feature/aitor/ff/enrollment branch from 2839a64 to e0cfb55 Compare June 10, 2025 21:39
Copy link
Contributor

@marcosholgado marcosholgado left a comment

Choose a reason for hiding this comment

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

LGTM

@aitorvs aitorvs marked this pull request as ready for review June 11, 2025 13:00
@aitorvs aitorvs merged commit 8fb8ca8 into develop Jun 11, 2025
6 checks passed
@aitorvs aitorvs deleted the feature/aitor/ff/enrollment branch June 11, 2025 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants