Description
Create the initial NestJS AnalyticsModule skeleton so subsequent analytics work has a home. This includes the module definition, an empty controller with a health-check style GET /analytics/ping route, and a service with a no-op method, wired into AppModule the same way ProgressModule is.
Why this matters
Every other analytics issue depends on this module existing and being registered in the app so routes and providers can be added incrementally.
Files to touch
backend/src/analytics/analytics.module.ts
backend/src/analytics/analytics.controller.ts
backend/src/analytics/analytics.service.ts
backend/src/app.module.ts
Acceptance Criteria
Notes
This issue is part of the new analytics module effort (tracking, aggregation,
and reporting on player/game activity). Please keep new code inside
backend/src/analytics/ following the same module/controller/service/provider
layout used by existing modules (e.g. progress, streak, quests).
Description
Create the initial NestJS
AnalyticsModuleskeleton so subsequent analytics work has a home. This includes the module definition, an empty controller with a health-check styleGET /analytics/pingroute, and a service with a no-op method, wired intoAppModulethe same wayProgressModuleis.Why this matters
Every other analytics issue depends on this module existing and being registered in the app so routes and providers can be added incrementally.
Files to touch
backend/src/analytics/analytics.module.tsbackend/src/analytics/analytics.controller.tsbackend/src/analytics/analytics.service.tsbackend/src/app.module.tsAcceptance Criteria
AnalyticsModulecompiles and is imported inAppModuleGET /analytics/pingreturns a 200 with a simple JSON payloadprogressandquestsNotes
This issue is part of the new
analyticsmodule effort (tracking, aggregation,and reporting on player/game activity). Please keep new code inside
backend/src/analytics/following the same module/controller/service/providerlayout used by existing modules (e.g.
progress,streak,quests).