admin/40227-vm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
40227-vm/backend/docs/user-progress.md
Dmitri d4a5378adf Refactor: migrate frontend to Vite/React, add product backend modules 
Frontend:
- Replace Next.js with Vite + React + TypeScript
- Add new component architecture (app-shell, sidebar, dashboard modules)
- Implement product modules: FRAME, safety protocols, walkthrough checkin,
  campus/staff attendance, personality quiz, sign language, classroom timer
- Add shadcn/ui component library with Tailwind CSS
- Remove legacy generated components, stores, and pages

Backend:
- Add product migrations: frame_entries, user_progress, safety_quiz_results,
  walkthrough_checkins, communication_events, personality_quiz_results,
  campus_attendance_config/summaries, staff_attendance_records, content_catalog
- Add corresponding models, services, and routes
- Implement cookie-based auth with refresh token rotation
- Add content catalog seeder with product content
- Migrate to ESLint flat config
- Switch from yarn to npm

Infrastructure:
- Update .gitignore for new tooling
- Add project documentation (CLAUDE.md, docs/)
- Remove deprecated config files and yarn.lock

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-06-09 15:18:23 +02:00

1.0 KiB
Raw Blame History

User Progress Backend

Purpose

user_progress stores current-user progress for narrow staff workflows such as learned sign language items and zone check-ins. The backend owns tenant scope, user ownership, and persistence.

API

All routes require JWT authentication.

  • GET /api/user_progress?progress_type=<type>: returns current user's progress rows for the requested type.
  • GET /api/user_progress?progress_type=<type>&item_id=<id>: returns current user's progress for one item.
  • POST /api/user_progress: creates or updates one progress item and returns the saved DTO.
  • DELETE /api/user_progress/by-item?progress_type=<type>&item_id=<id>: deletes current user's progress for one item.

Supported Initial Types

  • sign_learned
  • zone_checkin

Data Contract

Required mutation fields:

  • progress_type
  • item_id

Optional mutation fields:

  • value
  • score
  • metadata

The backend assigns organizationId, campusId, and userId from the authenticated user. Frontend-provided user names or roles are not trusted for ownership.