Skip to content

Scaffold the analytics module (module, controller, service) #479

Description

@phertyameen

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

  • AnalyticsModule compiles and is imported in AppModule
  • GET /analytics/ping returns a 200 with a simple JSON payload
  • Module follows the same folder layout as progress and quests

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).

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions