- removed exerciseRelease.plangId nullable, first step for #115

src/state/actions/ownOrGroupExerciseActions/releasesSiteActions/dialogs/changeExerciseReleaseDialog/setExerciseReleaseActions.ts

@@ -52,7 +52,7 @@ export function setGeneratedCode(generatedCode: string): SET_generatedCodeAction
   }
 }
 
-export function setPLangId(pLangId: number | null): SET_pLangIdAction {
+export function setPLangId(pLangId: number): SET_pLangIdAction {
   return {
     type: ActionType.SET_pLangId,
     pLangId

src/types/doExercise.ts

@@ -151,7 +151,7 @@ export interface ExerciseReleaseDoExerciseFromBackend {
   /**
    * the p lang for the release or NULL when released for all p langs
    */
-  readonly pLangId: number | null
+  readonly pLangId: number
 
   /**
    * true: assessment is finished, false: not

src/types/exercisePreview.ts

@@ -50,10 +50,9 @@ export interface ExercisePreviewFromBackend {
   readonly shouldNotCount: boolean
 
   /**
-   * the plang the release is for or null (released for all plangs)
-   * (can be null if not used in the exercise overview page)
+   * the plang the release is for
    */
-  readonly releasedForPLangId: number | null
+  readonly releasedForPLangId: number
 
   /**
    * the tags connected to this exercise

src/types/exerciseRelease.ts

@@ -68,15 +68,9 @@ export interface ExerciseReleaseBase {
   readonly hadAutomaticAssessmentErrors: boolean
 
   /**
-   * the plang to user can use or null then the user can solve the exercise in any plang (where a template is provided)
-   *
-   * with yapex 1.0 we no longer support any plang ... the user must select one
-   * (any plang is useless because normally we want X plangs and not all)
-   *
-   * null can only happen if plang is removed
-   * ... for further versions we may want to use on delete restrict so null is not longer possible but for now a workaround
+   * the plang to user can use
    */
-  readonly pLangId: number | null
+  readonly pLangId: number
 
   /**
    * Infinitely = 0, Limited = 1