-
Notifications
You must be signed in to change notification settings - Fork 218
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
MNTOR-3814 - use context to fetch experiment data from Cirrus #5440
base: main
Are you sure you want to change the base?
MNTOR-3814 - use context to fetch experiment data from Cirrus #5440
Conversation
Preview URL 🚀 : https://blurts-server-pr-5440-mgjlpikfea-uk.a.run.app |
nimbus_user_id: | ||
description: Nimbus user ID | ||
type: string | ||
nimbus_app_id: | ||
description: Nimbus application ID | ||
type: string | ||
nimbus_experiment: | ||
description: Nimbus experiment name | ||
type: string | ||
nimbus_branch: | ||
description: Nimbus branch | ||
type: string | ||
nimbus_experiment_type: | ||
description: Nimbus experiment type | ||
type: string | ||
nimbus_is_preview: | ||
description: Nimbus preview mode enabled | ||
type: string |
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.
Would we need to check in with a data steward to see if these metrics are still covered by our initial data review?
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.
Yes, so we may not be able to land this until that's done.
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.
Approving with the caveat that we are waiting on directions from a data steward. The code looks good to me and when giving this a spin locally it works as expected.
References:
Jira: MNTOR-3814
Description
This PR introduces an
ExperimentsContext
with a provider and auseExperiments()
hook that can be called by any client component that needs it. I implemented it just for Glean so far (per the linked Jira ticket) but if this approach is OK I can file a followup to move from prop-drilling to this more generally for features that need access to experiment data (which features are activated, what the active branch is, etc)How to test
I've been using the Glean debug dashboard to inspect pings. Note that local pings have
-1
for mostEnrollments
values, you need to use Cirrus (or something that mocks it). I'll see if I can mock this to add some automated tests.An easy way to inspect Glean pings is to run this in the browser devtools console:
Which should log:
Checklist (Definition of Done)