-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
fix: Isolate logic to expose js env variables sooner #8202
Conversation
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. |
This is a good solution but I am wondering if we should have better defaults for these env variables? I know that for METAMASK_BUILD_TYPE we can default to |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8202 +/- ##
=======================================
Coverage 40.30% 40.30%
=======================================
Files 1235 1235
Lines 29928 29928
Branches 2872 2872
=======================================
Hits 12062 12062
Misses 17173 17173
Partials 693 693 ☔ View full report in Codecov by Sentry. |
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
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.
LGTM
Description
When creating a new terminal and trying to run any of the building commands like
yarn setup
yarn watch
yarn start:android
andyarn start:ios
It would give an error that the environment variables are not loaded
The problem was that we were checking if the variables were loaded before they were actually loaded.
The solution is to load the variables as one of the first steps if they exist.
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist