Skip to content
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

chore(runway): cherry-pick feat: customize fetchInterval for remoteFeatureFlagController to 15min #13342

Merged
merged 1 commit into from
Feb 5, 2025

Conversation

runway-github[bot]
Copy link
Contributor

@runway-github runway-github bot commented Feb 4, 2025

Description

  • add a new app constant for the 15 min fetch interval
  • add fetch interval param using the constant
  • add test that controller builder function passes fetch interval param
  • remove out of scope unit tests (this was testing the controller. This
    is already tested in controller
    itself

    and adds a dangerous and blocking link to non local code.

Related issues

Fixes mobile app part of
https://github.com/MetaMask/MetaMask-planning/issues/4098

Manual testing steps

(Manual testing only be done by someone with Launch Darkly access)

  1. activate a remote feature flag
  2. Load app
  3. Check feature is activated
  4. disable remote feature flag
  5. Wait for 15 min
  6. Reload the app
  7. Check feature is deactivated

Screenshots/Recordings

Before

After

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the
    app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described
    in the ticket it closes and includes the necessary testing evidence such
    as recordings and or screenshots. 508a5f7

…atureFlagController to 15min (#13341)

## **Description**

- add a new app constant for the 15 min fetch interval
- add fetch interval param using the constant
- add test that controller builder function passes fetch interval param
- remove out of scope unit tests (this was testing the controller. This
is [already tested in controller
itself](https://github.com/MetaMask/core/blob/main/packages/remote-feature-flag-controller/src/remote-feature-flag-controller.test.ts)
and adds a dangerous and blocking link to non local code.

## **Related issues**

Fixes mobile app part of
MetaMask/MetaMask-planning#4098

## **Manual testing steps**

(Manual testing only be done by someone with Launch Darkly access)
1. activate a remote feature flag
2. Load app
3. Check feature is activated
4. disable remote feature flag
5. Wait for 15 min
6. Reload the app
7. Check feature is deactivated

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [x] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
@runway-github runway-github bot requested review from a team as code owners February 4, 2025 18:42
Copy link
Contributor

github-actions bot commented Feb 4, 2025

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@sethkfman sethkfman added the Run Smoke E2E Triggers smoke e2e on Bitrise label Feb 5, 2025
Copy link
Contributor

@sethkfman sethkfman left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

github-actions bot commented Feb 5, 2025

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 9a31f04
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/faa59324-b4b8-46f5-a441-5258b77e8e27

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

  • Check the documentation if you have any doubts on how to understand the failure on bitrise

@sethkfman sethkfman merged commit d30a58d into release/7.40.0 Feb 5, 2025
37 of 39 checks passed
@sethkfman sethkfman deleted the runway-cherry-pick-7.40.0-1738694534 branch February 5, 2025 17:34
@github-actions github-actions bot locked and limited conversation to collaborators Feb 5, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Run Smoke E2E Triggers smoke e2e on Bitrise team-runway-bot
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants