Extra work and potential future problems resulting from choosing an easy or limited solution now instead of using a better approach that might take longer or be more costly. Similar to financial debt, technical debt incurs "interest" that can make future changes more difficult and costly if not managed or "paid off."
Issue | Description | Priority | Impact | Estimated Effort | Notes |
---|---|---|---|---|---|
Migration outside of Loopback V3 | Medium | Epic | Authorization might be one of the biggest challenge during the migration. | ||
Remove legacy “drafts” code | Remove anything related to the legacy drafts (Draft model) | Low | ~8 points | ||
Lint - semi colon required | Add rule on linter configuration and add semi when is missing | Low | No impact | Easy | This issue can create some execution error like console.log(42) `1,2,3`.split(',') This code provide an error |
API - Routes | Create file for express routes. Currently, routes are on multiple files and create complex comprehension of routes | Medium | Possible regression | High | Need reverse engineering to get routes |
API - Separate handler | When routes will be create with express routes, we need to separate handler to simplify code and review | Medium | Possible regression | High | Same as routes. We can do this work by route. Once at a time |
All projects expect interface project - vscode or other software - add debug config | Add debug config will be facilitate code inspection and tracking issue | Very high | No impact | Medium | Need to list IDE who each team member using |
API - Unit tests | Two things - We need to simplify code and create unit tests on business code | High | Possible regression | Very high | |
Global - using ecmascript version | Unify javascript code for using module | High | Possible low regression, but if the code run, we have no impact | High | |
Global - Add jsdoc and comment | High | No impact | Very High | ||
Global - babel and jest | Remove jest and babel from global workspace. Place it on each project | Medium | Low | Medium | |
Global - Project structure | Project need to create a simple structure. Like simplify some API | Very High | Possible regression | Very High | When this work will be done, the project will be more simple |
Export scoresheet, reports on another repository | Each project should have own project. This task will simplify maintenance | Low | Low | High | |
Increase versions | Update node version, and libraries version to increase security | Very High | Big impact, need to retest all project | Very high | |
Python script to node script | Transform and export on another project python scripts on scripts/release_production.py by node script | Low | Low | Low | AWS lambda ? |
False imports | Some imports couldn,t be importable. This issue should be done after restructuring | Very low | Depends of structure | Depends of structure | Ex : require(`@hisports/web/babel.config`) |
File with certificate key | This file should be delete and not push on repository. We can ignore this file on gitignore and generate new pem file if isn’t here | Very high | Low | Low | |
TODO | Remove TODO and do TODO | Medium | Medium | High | |
Replace webpack by vite | Vite build fast and the bundle generated is light | Medium | Low | Medium | |
Replace MUI | Replace MUI and create our own ui kit | Very low | High | High | |
Check validity email | We need to check validity of email when user log in on Play | Very high | Very low | Low |