Interface, Not Abstract Class, For Mock Swap
A real and a mock service share a TypeScript interface that both implement, and the app config swaps one for the other at provider time:
ts
export interface OrdersApiInterface {
getOrders(): Observable<Order[]>;
// ...the public surface both implementations must honor
}
@Injectable()
export class OrdersApiService implements OrdersApiInterface { /* real */ }
@Injectable()
export class MockOrdersApiService implements OrdersApiInterface { /* mock */ }
// app config - one token, swap the implementation
{ provide: OrdersApiService, useClass: environment.useMocks ? MockOrdersApiService : OrdersApiService }Why
The mock and the real service keep one surface, held by the compiler.
How To Apply
- Declare an
interfacefor the service's public surface, named after its concept with anInterfacesuffix (XInterface), and writeimplementson bothXServiceandMockXService. - Swap via
useClassat the app-config layer. - An interface is erased at runtime, so it cannot be a DI token: keep the concrete service as the token, or inject an
InjectionToken<XInterface>when there is no natural default. - An
abstract classport only earns its keep when several production implementations coexist, never for mock substitution. implementson both sides makes the compiler enforce parity. With bare structural typing a missing method only bites at runtime.- An interface adds no inheritance, no runtime layer and nothing to construct, which keeps the DI seam simple.