Versions Compared

Key

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

Add your comments directly to the page. Include links to any relevant research, data, or feedback.

Page Properties
label
Impact

Status
colourRed
titleHIGH

Driver

Status

Status
colourGreen
title

Done

Decided

Decision leader

Oladimeji Onalaja (Unlicensed) 

Approver

Contributors

Panos Paralakis (Unlicensed) Tuomas Alahäivälä (Unlicensed) 

InformedTIS TeamDue dateOutcome

Date

 

Outcome

Bring all apps up to Angular v8 (variously from v1.2, v1.5, v5, v6, and v7). Remove jHipster dependencies. Move to standardised file structure. Tidy up SCSS folder. Tidy up Protractor and Cucumber tests. NGRX Observable.

Background

There's a lot of tech debt across TIS. In FE this is the case too.

...

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

Option 1:

Option 2:

Option 3:

Option 4:

Bringing all elements in TIS up to the same, current version of Angular

V5

V6

V7

V8

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) Admins UI is now Angular v6, but bringing Reval up to v6 is a large 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

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

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

Estimated cost

Status
colour

YELLOW

Yellow
titleMEDIUM

Status
colour

RED

Red
titleLARGE

Status
colour

RED

Red
titleLARGE

Status
colour

RED

Red
titleLARGE

Status

Status
colourYellow
titleIn progress
 - Admins UI 
Status
colourGreen
titledone
, Reval 
Status
colourRed
titleto do

Status
colour

YELLOW

Yellow
titlein progress
 - Admins UI 
Status
colourGreen
titledone
, Reval 
Status
colourRed
titleto do

Status
colourRed
titleto do

Status
colour

RED

Red
titleto do

Action items

Outcome

Bring all apps up to Angular v8 (variously from v1.2, v1.5, v5, v6, and v7). Remove jHipster dependencies. Move to standardised file structure. Tidy up SCSS folder. Tidy up Protractor and Cucumber tests. NGRX Observable.