Module courses 

The Courses tab: one row per course module with a course code, with its configuration validated.

Structs

AdminPauseCourseModulePayload

AdminResumeCourseModulePayload

CreditRegistrationCourseConfigCheck

What the configuration check concluded about one module, freshly derived from the same facts and the same rule the config-validation phase uses, with the course code verdict Suotar gave that phase.

CreditRegistrationCourseStats

CreditRegistrationStatsByCourse

Constants

COURSES_LIMIT 🔒

Modules with a course code, comfortably above any real deployment’s count. The only admin tab without a page or a limit of its own before this.

Functions

_add_routes

admin_pause_course_module_credit_registration

POST /api/v0/main-frontend/credit-registration-admin/courses/{course_module_id}/pause - Stops every phase from claiming this module’s rows.

admin_resume_course_module_credit_registration

POST /api/v0/main-frontend/credit-registration-admin/courses/{course_module_id}/resume - Lets the phases claim this module’s rows again.

get_credit_registration_stats_by_course

GET /api/v0/main-frontend/credit-registration-admin/courses - Every course module with a course code, its validated configuration and its volumes.

record_module_action 🔒

require_suotar_configuration 🔒

A module with no configuration row has nothing to pause: set_paused would update no rows and the call would report a pause that never happened.

to_course_stats 🔒