Add your comments directly to the page. Include links to any relevant research, data, or feedback.
Background
There's a lot of tech debt across TIS. In FE this is the case too.
Over time, some FE devs have tried to address the tech debt, with varying degrees of success and completion.
The result is an FE beast with duplicated elements in places, that need converging into one agreed solution, and multiple areas where the codebase needs bringing up the date (e.g. Angular 5 Apps containing non-Angular 5 code, and other Apps that aren't yet Angular 5 that need re-writing with Angular 5)
Relevant data
Things that need addressing are:
- Different versions of Angular in use
- Removal of dependency on jHipster scaffolding
- Aligning the filing structure to match best practice for Angular 5
- Tidy up the SCSS folder and code
- Where to apply global and local styles
- Tidying up of a plethora of tests and test approaches
- NGRX - observable
Options considered
| Option 1: | Option 2: | Option 3: | |
|---|---|---|---|
| Bringing all elements in TIS up to the same, current version of Angular | V5 | V6 | V7 |
| Pros and cons |
|
|
|
| Estimated cost | MEDIUM | LARGE | LARGE |
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
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 firstAction items
- Update Admins UI code to Angular v5
- TISNEW-2498: Re-write Angular 1.2/1.5 apps (Reval | Concerns Log | Notifications | Common Components) to Angular v5
- TISNEW-2503: Remove dependencies on jHipster scaffolding
- TISNEW-1650: Move to standardised file structure for Angular v5 - (Panos Paralakis (Unlicensed), Oladimeji Onalaja (Unlicensed), Tuomas Alahäivälä (Unlicensed) - does this need to be defined clearly somewhere, in order to give you all a consistent reference point?)
- Tidy up SCSS folder, files and code (Panos Paralakis (Unlicensed), Oladimeji Onalaja (Unlicensed), Tuomas Alahäivälä (Unlicensed) - does this need to be defined clearly somewhere, in order to give you all a consistent reference point?)
- Decide when global components are preferable, and where TIS would benefit from local styles
- Tidy up tests - protractor, cucumber, etc (Panos Paralakis (Unlicensed), Oladimeji Onalaja (Unlicensed), Tuomas Alahäivälä (Unlicensed) - does this need to be defined clearly somewhere, in order to give you all a consistent reference point?)
- NGRX - observable (Panos Paralakis (Unlicensed), Oladimeji Onalaja (Unlicensed), Tuomas Alahäivälä (Unlicensed) - please urn this item into a specific action)
Add Comment