Contents
PR Summary
What problems was I solving
The leadmagic-client package exposed three environment-config utilities (LeadmagicClientEnvConfigSchema, type LeadmagicClientEnvConfig, and parseLeadmagicClientEnvConfig) that were never consumed anywhere in the monorepo. They added an unnecessary public surface area and could mislead future callers into thinking the client is initialized from env vars rather than from the plain LeadmagicClientConfig object it actually requires.
What user-facing changes did I ship
None. The client constructor and the rest of the exported API remain unchanged; only unused internal/exported env-config helpers were removed.
How I implemented it
Deleted architect/leadmagic-client/main/leadmagic-client-config.ts and removed the corresponding re-exports from architect/leadmagic-client/main/index.ts. No other code, tests, or dependencies required updates because the constructor path for LeadmagicClient already takes a raw apiKey, optional baseUrl, and optional timeoutMs directly.
Description for the changelog
Removed the unused LeadmagicClientEnvConfigSchema, LeadmagicClientEnvConfig, and parseLeadmagicClientEnvConfig exports from leadmagic-client. The public LeadmagicClient interface is unchanged and continues to accept LeadmagicClientConfig with a raw API key.