Skip to content

Upgrade to Angular 9

What does this MR do?

We are upgrading the angular version to Angular 9.

Angular 9 also introduces many new features and a new compiler.

There are some issues to fix before this is ready for master; we have to

~"To Do"

  • Fix some tests that are failing
  • Fix charts whose styling is messed up
  • Add browserlist file so that angular can adapt css and js accordingly
  • Double check that everything works.
  • Update node.js version to dubnium in .gitlab-ci.yml
  • Fix sidebar items not being shown

Related issues and links

Fix #399 (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 Stella Rouzi

Merge request reports