| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Warning
This PR refactors and centralizes environment-variable handling by introducing ReadOnlyEnv alongside a writable Env, moving GitHub Actions env-var constants into environment.ts, and updating key helpers/tests to support environment injection (defaulting to getEnv() for compatibility).
Changes:
| File | Description |
|---|---|
| src/environment.ts | Introduces ReadOnlyEnv/Env classes, adds ActionsEnvVars, and expands EnvVar constants. |
| src/util.ts | Removes local env helper implementations and re-exports env helpers for backwards compatibility. |
| src/actions-util.ts | Switches env access to the new Env abstraction and threads an injectable env through several helpers. |
| src/api-client.ts | Allows getApiDetails/getApiClient to read required env vars via an injected ReadOnlyEnv. |
| src/testing-utils.ts | Updates test helpers to support setting Actions env vars via Env. |
| src/api-client.test.ts | Updates tests to pass a test environment object rather than stubbing required env param helpers. |
| src/setup-codeql.test.ts | Uses EnvVar constants for Code Scanning PR env vars. |
| src/init.test.ts | Uses ActionsEnvVars constant for RUNNER_ENVIRONMENT. |
| src/autobuild.ts | Uses ActionsEnvVars.RUNNER_ENVIRONMENT instead of a raw string lookup. |
| src/config/remote-file.ts | Switches ActionsEnvVars import to environment.ts. |
| src/config/remote-file.test.ts | Switches ActionsEnvVars import to environment.ts. |
| lib/entry-points.js | Generated JS output change (not reviewed; diff content excluded by policy). |
Sorry, something went wrong.
| export function getTemporaryDirectory(env: Env = getEnv()): string { | ||
| return ( | ||
| env.getOptional(EnvVar.TEMP) ?? env.getRequired(ActionsEnvVars.RUNNER_TEMP) | ||
| ); |
There was a problem hiding this comment.
Makes sense.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM ![]()
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR cherry-picks some changes from #3994 and addresses review feedback there related to the new Env abstraction.
Main changes
Out of scope
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
Products:
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist