sdedieu
**Summary** The NSwag Angular template generates services ([@Injectable](https://angular.dev/api/core/Injectable)) that use [HttClient](https://angular.dev/api/common/http/HttpClient) and expose `Observable<Data>`. The future of Angular is to expose [Resources](https://angular.dev/api/core/resource) instead. **Describe the solution you'd like** I'd like to see generated client using [httpResource](https://angular.dev/guide/http/http-resource) rather than [HttClient](https://angular.dev/api/common/http/HttpClient). Benefits are that [Resources](https://angular.dev/api/core/resource) contains more informations than data👇 ``` interface [Resource](https://angular.dev/api/core/Resource)<T> { readonly value: [Signal](https://angular.dev/api/core/Signal)<T>; readonly status: [Signal](https://angular.dev/api/core/Signal)<[ResourceStatus](https://angular.dev/api/core/ResourceStatus)>; readonly error: [Signal](https://angular.dev/api/core/Signal)<Error | undefined>; readonly isLoading: [Signal](https://angular.dev/api/core/Signal)<boolean>; readonly snapshot: [Signal](https://angular.dev/api/core/Signal)<[ResourceSnapshot](https://angular.dev/api/core/ResourceSnapshot)<T>>; hasValue(this: T extends undefined ? this : never): this is [Resource](https://angular.dev/api/core/Resource)<Exclude<T, undefined>>; hasValue(): boolean; } ``` **Describe alternatives you've considered** An alternative could be to keep [HttClient](https://angular.dev/api/common/http/HttpClient) but to use [rxResource](https://angular.dev/api/core/rxjs-interop/rxResource) to map the exposed `Observable<Data>` into [Resources](https://angular.dev/api/core/resource). It is less clean but lead to the same result.