Service Decorator nutzen (#99)

Author: d-koppenhagen

blog/2025-10-signal-forms-part1/README.md

@@ -5,7 +5,7 @@ mail: mail@d-koppenhagen.de
 author2: Ferdinand Malcher
 mail2: mail@fmalcher.de
 published: 2025-10-13
-lastModified: 2026-02-21
+lastModified: 2026-05-21
 keywords:
   - Angular
   - Signals
@@ -262,9 +262,9 @@ To demonstrate this, we want to simulate a registration process that involves a
 This service method returns a `Promise` that resolves after a two-second delay, simulating a network request.
 
 ```typescript
-import { Injectable } from '@angular/core';
+import { Service } from '@angular/core';
 
-@Injectable({ providedIn: 'root' })
+@Service()
 export class RegistrationService {
   registerUser(registrationData: Record<string, any>) {
     return new Promise((resolve) => {

blog/2025-10-signal-forms-part2/README.md

@@ -5,7 +5,7 @@ mail: mail@d-koppenhagen.de
 author2: Ferdinand Malcher
 mail2: mail@fmalcher.de
 published: 2025-10-15
-lastModified: 2026-02-21
+lastModified: 2026-05-21
 keywords:
   - Angular
   - Signals
@@ -321,7 +321,7 @@ To simulate an asynchronous server call, we extend our `RegistrationService` wit
 If the username is `johndoe`, we consider it taken, and the operation resolves to `true`.
 
 ```typescript
-@Injectable({ providedIn: 'root' })
+@Service()
 export class RegistrationService {
   checkUserExists(username: string) {
     return new Promise<boolean>((resolve) => {

material/interceptors/README.md

@@ -1,7 +1,7 @@
 ---
 title: 'Interceptors: HTTP-Requests erfassen und transformieren'
 published: 2026-03-06
-lastModified: 2026-03-06
+lastModified: 2026-05-21
 sortKey: 10
 ---
 
@@ -359,9 +359,9 @@ Diesen Ansatz wollen wir mit einem eigenen Service nachbilden.
 
 ```typescript
 // auth.service.ts
-import { Injectable, signal } from '@angular/core';
+import { Service, signal } from '@angular/core';
 
-@Injectable({ providedIn: 'root' })
+@Service()
 export class AuthService {
   private _isAuthenticated = signal(true);
 

material/resolvers/README.md

@@ -1,7 +1,7 @@
 ---
 title: 'Resolvers: Daten beim Routing vorladen'
 published: 2026-05-17
-lastModified: 2026-05-17
+lastModified: 2026-05-21
 sortKey: 11
 ---
 
@@ -340,11 +340,11 @@ Wenn die Daten bereits im Speicher liegen und kein HTTP-Request mehr nötig ist,
 Ein Beispiel: Wir haben einen `ConfigService`, der die Konfiguration beim Start der Anwendung einmalig lädt und anschließend aus dem Cache liefert:
 
 ```typescript
-import { Injectable, inject } from '@angular/core';
+import { Service, inject } from '@angular/core';
 import { HttpClient } from '@angular/common/http';
 import { shareReplay } from 'rxjs';
 
-@Injectable({ providedIn: 'root' })
+@Service()
 export class ConfigService {
   #http = inject(HttpClient);