[UI] adds Hedy dashboard & common error detection

[karlijnbok]

Description

• Adds a button to the for-teachers/class/{{class_info.id}} page to open the live statistics dashboard.
• Adds a live statistics dashboards page at /live_stats/class/{{class_info.id}}.

[ghost]

👇 Click on the image for a new way to code review

Legend

[Felienne]

class_live I think is a new babel string? Be sure to run the pybabel extraction command (see docs) so it will be added to the pot files and can be translated.

[jpelay]

I changed the way the misconceptions are gathered. I changed the name to exception types (suggestion by @Felienne) and also made them language independent by using the already tracked exceptions per program. This means that the error_history field is not used anymore and it can be removed what do you think @Felienne.

Also, I haven't realized before that the commor exceptions types per class were stored in the customizations table. This is a bad idea, because they are two conceptually different entities, and also if the teacher deletes the customizations they will also delete this important bit of their class information! So I think this should go to the classes table. I wil ldo that tomorrow.

[Felienne]

I changed the way the misconceptions are gathered. I changed the name to exception types (suggestion by @Felienne) and also made them language independent by using the already tracked exceptions per program. This means that the error_history field is not used anymore and it can be removed what do you think @Felienne.

Yes, better to remove that field it was a bit of a weird way of storing!

Also, I haven't realized before that the commor exceptions types per class were stored in the customizations table. This is a bad idea, because they are two conceptually different entities, and also if the teacher deletes the customizations they will also delete this important bit of their class information! So I think this should go to the classes table.

Ah what a good catch @jpelay!! This indeed should be stored elsewhere. Maybe on the student rather than on the class (or on the program) after which we can gather them per student/per class (potentially with some caching in the DB otherwise it'll be too expensive?)

I wil ldo that tomorrow.

<3

[jpelay]

Ah what a good catch @jpelay!! This indeed should be stored elsewhere. Maybe on the student rather than on the class (or on the program) after which we can gather them per student/per class (potentially with some caching in the DB otherwise it'll be too expensive?)

Sorry, I don't I don't fully understand this 😅. For clarification you mean storing the groups of exceptions a student have incurred per student right?

Right now they're stored line this:

"class": {
  "common_errors": [
      {
          "label": "invalid_command_exception",
          "active": 1,
          "students": ["student1", "student2"]
      }
   ]
}

In which table do you think we could store this information? These groups are already gathered every time the teacher access the Class live page, they are actually being recomputed every time, they're stored in the database only in case the teacher decides to ignore that specific group of exceptions.

[jpelay]

I created a new table where we store the common errors for a class. This table has the following structure:

"class_errors": [
    {
      "id": "5c39c2a936f24db1a4935c52fab77cd7", // the class id
      "errors": [
        {
          "id": 0,
          "label": "invalid_command_exception", // the label of the exception group. Must be messages.pot
          "active": 0, // weather the exception is shown to the teacher
          "students": [
            "student1" // list of students that have incurred in this group of exceptions
          ]
        }
      ]
    }
]

Also, I created a new function for better handling of the class customizations. I tested the page with classes with no customizations and it works now.

[jpelay]

I don't know if this is really necessary. This enforces a limit of 10 exception groups per class, so if the students of a class have made exceptions belonging to 10 different groups, it'll delete the 5 previous ones to make room for new. I think this is for not to clutter the UI. What do you think, @Felienne, do we leave this?

[jpelay]

With that said, @Felienne this is done!!!

Everything is now good to go!

[Felienne]

Hi @karlijnbok!!

It took a while but we are ready to merge this, and it will appear on the website soon! Thanks a lot on behalf of the Hedy team!!

[Felienne]

Let's go!

[mergify]

Thank you for contributing! Your pull request is now going on the merge train (choo choo! Do not click update from main anymore, and be sure to allow changes to be pushed to your fork).