Release Candidate : 1.0.0 #150
Reference in New Issue
Block a user
Delete Branch "release/1.0.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
- GET /promotions/{idPromo} returns promotion or 404 - PUT /promotions/{idPromo} updates year or 404 - DELETE /promotions/{idPromo} deletes promotion or 404 - Only employees allowed, otherwise 403Implement GET, PUT, DELETE for /modules/{idModule} with 404 handling.Add CRUD API for enseignements (prof-module-promo associations): - POST /enseignements: Create with validation (201/409) - GET /enseignements/{idProf}/{idModule}/{idPromo}: Read by composite key (200/404) - DELETE /enseignements/{idProf}/{idModule}/{idPromo}: Delete by composite key (204/404) Access control: Employee-only (403 Forbidden) Tests: 7 unit tests added Note: RBAC implementation pending (current access control is temporary)- Replace flat file `[idProf]_[idModule]_[idPromo].ts` with nested structure `[idProf]/[idModule]/[idPromo].ts` - Ensures URL matches `/enseignements/{idProf}/{idModule}/{idPromo}`- GET /ajustements/{numEtud}/{idUE}: get ajustement by student numEtud and UE id - Requires employee role- PUT /ajustements/{numEtud}/{idUE}: update ajustement valeur - Requires employee role- DELETE /ajustements/{numEtud}/{idUE}: remove ajustement from DB - Requires employee role - Returns 204 on success- GET /ue-modules/{idModule}/{idUE}/{idPromo}: recover the detail of an ue-module association by its composite key - requires employee role- PUT /ue-modules/{idModule}/{idUE}/{idPromo}: update coeff for UE-Module-Promo association - DELETE /ue-modules/{idModule}/{idUE}/{idPromo}: remove UE-Module-Promo association - requires employee role