Angular client

[vytautas-pranskunas-]

Description

It would be nice to have angular client rather than legacy-angular

[mrlubos]

@vytautas-pranskunas- I actually realised I don't understand the requirements here. What would you expect from the new Angular client?

[vytautas-pranskunas-]

I dont remember yet wat was my idea. Need to look at the code but in some ways it was obviously legacy. Sry for miss of the details. However i am not using it anymore because if that and i wrote my own openai to typescript generator

[max-scopp]

@vytautas-pranskunas- Jumping in here! Personally, I think (as reflected in my plugin PR) that simply having an Angular client doesn’t fully address the core issue. While it reduces boilerplate for data fetching, the challenge of async data handling remains. My PR with the TanStack plugin tackles this more effectively (for a deeper look, check out this video: YouTube Link).

Using this plugin might feel unconventional since it bypasses Angular’s HttpClient, but it achieves the main objective: Signals that directly reflect the current or pending server state.

If you still prefer to stick with HttpClient, one option is to replace the default fetch() in @hey-api/client-fetch with Angular’s HttpRequest and HttpResponse wrappers. However, since Angular 16, HttpClient uses fetch() under the hood by default, making this adaptation somewhat redundant.

For most cases (unless the project is unusually outdated), it might be more effective to bypass HttpClient altogether. The benefits of HttpClient are already well-covered by @hey-api/client-fetch and TanStack Angular Query.

[mrlubos]

Putting the "info needed" label on this thread. If anyone who upvoted it can describe what's the required functionality, that would be appreciated!