You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background: The README describes a "typed configuration layer" validating EXPO_PUBLIC_API_URL and EXPO_PUBLIC_CHAIN_ID at startup, throwing a developer-facing error if missing/invalid rather than silently falling back to production defaults.
Problem: This safety-critical startup validation logic has no documented/visible test coverage, risking silent regressions that reintroduce unsafe fallbacks.
Expected outcome: A dedicated test file verifying: missing var throws, malformed URL throws, invalid chainId (non-numeric or unsupported) throws, and valid config passes through unchanged.
Suggested implementation: Locate the config module (likely src/config/ or src/lib/config.ts), write Vitest cases mocking process.env/Constants.expoConfig.extra, assert thrown error messages are actionable.
Acceptance criteria: All four scenarios above are covered; tests fail if fallback-to-production-default behavior is reintroduced; pnpm typecheck remains clean.
EXPO_PUBLIC_API_URLandEXPO_PUBLIC_CHAIN_IDat startup, throwing a developer-facing error if missing/invalid rather than silently falling back to production defaults.chainId(non-numeric or unsupported) throws, and valid config passes through unchanged.src/config/orsrc/lib/config.ts), write Vitest cases mockingprocess.env/Constants.expoConfig.extra, assert thrown error messages are actionable.pnpm typecheckremains clean.src/(config module),tests/test,good first issue,GrantFox OSS,Maybe Rewarded,Official Campaign | FWC26