Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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

  • No labels