29 lines
1.3 KiB
Markdown
29 lines
1.3 KiB
Markdown
# Temporarily Disabled Modules
|
|
|
|
The backend currently omits two partially implemented modules from the runtime
|
|
NestJS configuration so that the public API surface only exposes completed
|
|
features.
|
|
|
|
## Cases Module
|
|
|
|
- Removed from `AppModule` and `apiRoutes` to ensure the unfinished `/cases`
|
|
endpoints are not routable.
|
|
- All existing code remains in `apps/bff/src/modules/cases/` for future
|
|
development; re-enable by importing the module in
|
|
`apps/bff/src/app.module.ts` and adding it back to the router configuration in
|
|
`apps/bff/src/core/config/router.config.ts` once the endpoints are ready.
|
|
|
|
## Jobs Module
|
|
|
|
- Temporarily excluded from `AppModule` while the reconciliation workflows are
|
|
fleshed out.
|
|
- The BullMQ processor now logs an explicit warning and acknowledges each job so
|
|
queue workers do not hang when the module is re-registered.
|
|
- When background processing is ready, restore the `JobsModule` import in
|
|
`apps/bff/src/app.module.ts` and replace the placeholder logic in
|
|
`ReconcileProcessor.process` with the real reconciliation implementation.
|
|
|
|
> **Note**: If additional queues or HTTP routes reference these modules, make
|
|
> sure they fail fast with a `501 Not Implemented` response or similar logging so
|
|
> that downstream systems have clear telemetry while the modules are disabled.
|