Skip to content

Add alert to inform the user about the signign app

What does this MR do?

This MR show the user an alert to inform them about the signing app

I added a section at the grades screen to. The user can remove this section by pressing "skip". This information is stored at the user storage.

This MR requires access to the user storage from teachers.

This MR assumes that at some point there will be a TutrorialService that will handle these type of information. For now this logic exist in the component

Extra configuration is required for the installation supported platforms at the app.json. More information can be found at src/app/courses/components/courses-details/course-details-exam-signing-app-alert/course-details-exam-signing-app-alert.d.ts

Example:

"signingAppInstructions": [
        {
          "alternateName": "windows",
          "name": "Windows",
          "url": "url",
          "expression": "win",
          "default": true
        },
        {
          "alternateName": "linux",
          "name": "Linux",
          "url": "url",
          "expression": "linux"
        },
        {
          "alternateName": "mac",
          "name": "MacOS",
          "url": "url",
          "expression": "mac"
        }
      ]

Related issues and links

Fix #290 (closed)

Other relevant links

Developer Checklist

  • I have successfully run the code of this merge request locally

  • I have verified locally that my changes work for all necessary screen sizes

  • I have tried out the changes of this MR with different users to identify bugs

  • Coding is in progress, and I have marked the MR as WIP

  • Coding is completed and the MR is ready for review

  • My branch is up-to-date with the upstream master branch

  • My MR follows the contribution guidelines

  • I have added a comment with screenshots of the code running locally

Tech review Checklist

Have you verified that what is supposed to happen, actually does, and what is not supposed to happen, indeed does not?

  • The MR accurately describes the changes and has a relevant title/description
  • The MR does what it is supposed to according to its title, description and related issues/links
  • I have successfully run the changes locally, and tried the new code

Overall review Checklist

  • The MR references related issues/MRs
  • The MR provides links to screens and screenshots
  • The commits of the MR describe the changes, have proper wording, and follow the guidelines
  • I have successfully run the changes locally, and tried the new code
  • The MR is ready for merge (rebased, commit squashed if needed, etc)
Edited by Dimitrios Pliakos

Merge request reports