Support Angular `httpResource` API

[martinboue]

Context

Angular is transitioning to signals and since v19.2 Angular has introduced httpResource async signal.

As of v20.1 httpResource is still experimental but it will become the recommended way to fetch data when stable.

Current behavior

Orval exposes Observable<T> from HttpClient for every request.

Expected behavior

Expose httpResource's signal, Observable<T> or both for every GET requests. Ideally it should be configurable.

Keep the current behavior for other HTTP verbs (POST, PUT, ...).

[melloware]

cc @snebjorn

[snebjorn]

Yeah it's also on my wishlist. Personally I'd like some experience with httpResource and wait for stable before I start on the feature.
But that's not going to stop anyone else :)

[knutmarius]

Any updates on this? Would be really nice to get HTTP Resource support!

[snebjorn]

I have no plans before it's stable. But PRs are welcome.

[melloware]

@ScriptType any thoughts on this or should we close it since we supprot TanStack Query for Angular now?

[the-ult]

Would be really nice if the new Angular httpResource was supported.
This would work great in combination with ngrx/signals store withResource

[ScriptType]

@melloware i for myself think httpResource is inferior to tanstack-query.
BUT its build in so it would be really nice if we support this, but currently it is in experimental and angular likes to change the api.

And even the withResource form ngrx has some problems with type-narrowing with it at the moment.
I would wait till it is atleast in developer preview, which is defined like this in angular

"Occasionally we introduce new APIs under the label of "Developer Preview". These are APIs that are fully functional and polished, but that we are not ready to stabilize under our normal deprecation policy."

[melloware]

I have no dog in this fight 😄

[the-ult]

Added a PR, to add httpResource functionality. #2923