Handling HTTP call side effects with Angular Signals

For now, we have rxResource which is the reactive way for calling an Observable API when the source signals change. The resource API of Angular is mean't only for non mutation operations (GET Alone).

But when dealing with traditional Create, Update, Delete, Patch, any other request type other than GET. We have to use the traditional API subscribe and perform actions alone.

So looking at your scenario, the best we can do for now, is maybe convert the form to a signal form, that is if you must use signals.

But from the code shared, you are already using the correct code as on 27-02-2026.

That is until we get a reactive counterpart like rxResource for all methods other than GET.

So start using resource API for all fetch requests, signal forms for newly created forms and all signal features for your application. The non GET API operations remain as is.

Ah, ok - I was struggling because I used the Angular MCP Server to try and migrate my code, but the result made it so I kept getting an ExpressionChangesAfterChecked when my success message tried to display. I thought I needed to change how I was handling the side effects of the HTTP call, but now I think maybe it was something else. I undid the MCP Server's changes and am just going to do it manually bit by bit. Thanks!