mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-18 21:16:47 +00:00
Maurice
3d522be0e5
The routes lived in reservations/ while the SQL lived on DaysService, so the controller delegated every call across a domain boundary to reach its own data, and neither module owned the thing outright. The seven statements move into AccommodationsService unchanged and the domain gets its own directory, module, DTO, RPC and MCP surface. What stays in days/ is the reorder side: assertNoInvertedAccommodation and resyncAccommodationDays are about re-dating day rows, and the stay is the thing being carried, not the thing doing the carrying. Two edges fall out of this. AccommodationsService drops its DaysService dependency, and DaysMcp drops DatabaseService and PlacesService, because create_place_accommodation was their only user - which lets DaysModule stop importing PlacesModule and closes one leg of the latent Days -> Places -> Assignments -> Days cycle. DAY-SVC-016..026, 029 and 035 move to accommodations.service.test.ts with their case ids intact. The reservations e2e container assembles both modules now: it builds a single domain module on purpose, which is exactly what catches a move like this, and it caught it.
30 lines
1.5 KiB
TypeScript
30 lines
1.5 KiB
TypeScript
import { Module } from '@nestjs/common';
|
|
import { AccommodationsController } from './accommodations.controller';
|
|
import { AccommodationsService } from './accommodations.service';
|
|
import { AccommodationsRpc } from './accommodations.rpc';
|
|
import { AccommodationsMcp } from './accommodations.mcp';
|
|
import { PlacesModule } from '../places/places.module';
|
|
import { AuthModule } from '../auth/auth.module';
|
|
import { DatabaseModule } from '../database/database.module';
|
|
import { PermissionsModule } from '../permissions/permissions.module';
|
|
import { RealtimeModule } from '../realtime/realtime.module';
|
|
import { PluginGuardsModule } from '../plugins/host/plugin-guards.module';
|
|
|
|
/**
|
|
* Accommodations. One fachlichkeit, one module: the routes used to sit in
|
|
* reservations/ while the SQL sat on DaysService, so neither module owned the
|
|
* thing outright and every call crossed a domain boundary to reach its own data.
|
|
*
|
|
* It imports neither days nor reservations. The stay rows reference days by id,
|
|
* which is a foreign key, not a module edge. PlacesModule is here only because
|
|
* create_place_accommodation writes a place and a stay in one transaction --
|
|
* the same reason DaysMcp could drop it.
|
|
*/
|
|
@Module({
|
|
imports: [PermissionsModule, RealtimeModule, PluginGuardsModule, DatabaseModule, PlacesModule, AuthModule],
|
|
controllers: [AccommodationsController],
|
|
providers: [AccommodationsService, AccommodationsRpc, AccommodationsMcp],
|
|
exports: [AccommodationsService],
|
|
})
|
|
export class AccommodationsModule {}
|