Alex Rickabaugh

This issue is resolved by the [`withRequestsMadeViaParent()`](https://angular.io/api/common/http/withRequestsMadeViaParent) feature for `provideHttpClient()`.

Agreed. If anyone wants to send a PR, that would be awesome 😄

Wow, I was asleep this morning. Last sentence should be: Perhaps docking with a craft that's been modified in the future (either by having resources shifted around, or having other...

@zaiddabaeen currently, this is by design. Typescript needs to be able to infer the `observe` and `responseType` values statically, in order to choose the correct return type for `get()`. If...

@zaiddabaeen the problem is for: ```javascript const res = this.http.get(url, options); ``` What is the type of `res`? It depends on the values in `options` - but Typescript has no...

Closing, the solution is to pass a correctly typed argument.

@nortain you definitely don't need either. ```javascript this.httpClient.post(url, data, {responsesType: 'text'}) ``` will give you an `Observable` without you having to specify ``. You don't need to say `'text' as...

@tobihagemann `responseType: 'text' as 'text'` is what you want. `'text'` is not `'json'`.

Closing as we have no plans to support coordinated type-checking of multiple structural directives, but `@switch` does support type-checking (it's about time!)

DI in Angular is lazy by design. _All_ services (not just `providedIn: 'root'`) are lazy and are only instantiated when requested. `eager: true` is not an option we can support...