Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page Properties
label


Status
Status
colourYellow
titleIn progress
Impact

Status
colourRed
titleHIGH

DriverOladimeji Onalaja (Unlicensed) 
ApproverAndy Nash (Unlicensed)
ContributorsPanos Paralakis (Unlicensed) Tuomas Alahäivälä (Unlicensed) 
InformedTIS Team
Due date
Outcome


Background

...

Things that need addressing are:

  1. Different versions of Angular in use
  2. Removal of dependency on jHipster scaffolding
  3. Aligning the filing structure to match best practice for Angular 5
  4. Tidy up the SCSS folder and code
  5. Where to apply global and local styles
  6. Tidying up of a plethora of tests and test approaches
  7. NGRX - observable

Options considered

DescriptionYELLOWMEDIUM

Option 1:Option 2:Option 3:
Bringing all elements in TIS up to the same, current version of AngularV5V6

V7

Pros and cons

(plus) Admins UI is v5 and the biggest element of TIS. Getting everything to v5 would mean we could then upgrade all of TIS to later versions of Angular more easily

(minus) v5 is already 2 full versions behind the current stable version of Angular (v7). Admins UI contains lots of non-Angular v5 code within it that will need to be converted to Angular v5 first

(plus) More modern version of Angular opens up new features and addresses issues from v5

(minus) No element is using Angular v6 yet, so bringing all of TIS up to v6 is a huge task

(plus) More modern version of Angular opens up new features and addresses issues from v6

(minus) No element is using Angular v7 yet, so bringing all of TIS up to v7 is a huge task

Estimated cost
Status
colourYELLOW
titleMEDIUM
Status
colourRED
titleLARGE
Status
colour
RED
title
LARGE

Action items

Outcome