[sentry-junior]

This adds a per-request base URL hook to the generated client, so a host can send each org-scoped request to the org's region or server before the URL is built. Follow-up to #129, which gave CredentialProvider.current the path's scope. That only helps pick a credential for a URL that's already built.

const sentry = createSentryClient({
  baseUrl: "https://sentry.io",
  resolveBaseUrl: async ({ baseUrl, scope }) =>
    scope ? await regionUrlFor(scope.organization) : baseUrl,
});
await sentry.listOrganizationIssues({ path: { organization_id_or_slug: "acme" } });
// → https://us.sentry.io/api/0/organizations/acme/issues/

What changes

• Config.resolveBaseUrl (types BaseUrlRequest and BaseUrlResolver, exported from the root). It receives { baseUrl, url, scope? }:

  • baseUrl is the configured base URL, or '' when none is set.
  • url is the built path and query.
  • scope is parseApiPathScope(url), and is left out for unscoped paths.

  Its result replaces baseUrl for that one request, with trailing slashes removed. It runs once per request, including prepareRequest, after requestValidator and before request interceptors. A per-call resolveBaseUrl replaces the configured one. If it throws, the request rejects with that error unchanged and fetch is never called.

• The new step lives in scripts/generate-base-url-resolver.mjs. It patches the pinned Fetch client in the same way generate-request-preparation.mjs does.

• parseApiPathScope moves to lib/api-client/api-path-scope.ts, a module with no imports, so the generated client can use it without bundling errors.ts. api-path.ts re-exports it, so the public API doesn't change.

The host still owns region discovery, caching, and trust. The client only asks the host which base URL to use.

Consumer

The toolkit CLI will use this to replace resolveOrgRegion calls at each call site and the getDefaultSdkConfig({ path }) workaround from getsentry/toolkit#1978. I built that change against a local build of this branch. CLI tsc, lint, and the affected tests pass.

Tests

test/base-url-resolution.test.ts covers:

• An org-scoped operation goes to the resolved base URL. The resolver gets the base URL, path, query, and scope.
• A project scope is passed through. Unscoped paths get no scope key.
• Raw prepareRequest URLs are resolved, including when no baseUrl is configured.
• Ordering: the resolver runs after validation, before interceptors, and once per request.
• A per-call resolver overrides the configured one.
• A resolver that throws rejects the request before any fetch.

pnpm build, pnpm typecheck, and pnpm test (632 tests) pass.

via @BYK.

--

View Session in Sentry