[klerick]

A provider built inside a nested component gets its own SDK config while the
interceptors stay global, and nothing told them apart — every request looked the
same whichever provider made it. The config may now carry an HttpContext.

const SCOPE = new HttpContextToken<string>(() => 'root');

@Component({
  providers: [
    provideJsonApi(() => ({
      apiHost: '…',
      httpContext: new HttpContext().set(SCOPE, 'nested'),
    })),
  ],
})

A global interceptor then reads req.context.get(SCOPE) as usual.

Two commits

97f9ce0 — the translation, and a bug it was hiding. Angular's HttpClient
was injected as HttpInnerClient directly, with an as any papering over the
fact that the two disagree about argument positions:

	HttpInnerClient	HttpClient
get	(url, { params })	(url, options)
post / patch	(url, body)	(url, body, options)
delete	(url, body?)	(url, options) — body goes inside

delete is the one that cost something: deleteRelationships handed
{ data: [...] } to the slot meant for headers, params and context, so the body
never reached the request. The fetch client reads that argument as a body, so it
only ever went wrong under Angular. post/patch were harmless but equally
misaligned — which is also why nothing could be attached to a request until now.

An adapter in the Angular file translates the four verbs, leaving the fetch and
axios adapters untouched.

e5f513d — the context. Attached to every verb, in whichever argument that
verb keeps its options in.

Shape

HttpContext stays out of JsonSdkConfig: the core keeps no Angular types, or
it would reach the fetch and axios builds where it means nothing. The Angular
file extends it as JsonSdkAngularConfig instead.

The config is now resolved once, behind an internal token. Three providers
read it, and a config factory called once per provider would have handed
JsonApiSdkService and AtomicFactory two different HttpContext objects —
the exact thing this feature exists to make comparable.

Tests

Written first, red before each commit. They assert the arguments the adapter
hands to HttpClient, verb by verb: that a delete body arrives as { body },
that post/patch keep the body in its own argument, that the context reaches
all four, that params and body survive alongside it, and that a config
without a context adds nothing.

The spec imports @angular/compiler first — loading @angular/common/http
outside an AOT build leaves its providers to be JIT-compiled, and without it the
import fails.

Verified green: unit across 9 projects, ts-test, e2e 137/137 on both MikroORM
and TypeORM. json-api-front:build:production fails on a CSS budget, as on
master.

🤖 Generated with Claude Code

[nx-cloud]

View your CI Pipeline Execution ↗ for commit e5f513d

Command	Status	Duration	Result
nx affected --target=build --parallel=3 --exclu...	✅ Succeeded	1s	View ↗
nx run json-api-server-e2e:e2e-micro --parallel=1	✅ Succeeded	1m 15s	View ↗
nx run json-api-server-e2e:e2e --parallel=1	✅ Succeeded	1m 14s	View ↗
nx run json-api-server:build:development	✅ Succeeded	1s	View ↗
nx affected --target=ts-test --parallel=3 --pas...	✅ Succeeded	<1s	View ↗
nx affected --target=test --parallel=3 --passWi...	✅ Succeeded	1s	View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗

---

☁️ Nx Cloud last updated this comment at 2026-10-10 12:51:05 UTC