Integrate Typescript | Back End

[NicolasOmar]

Objective

Integrate Typescript technology into the project's code.

---

Description

To revitalize the project and ease the development experience (after gathering new information from past and current projects), I decided to include Typescript as part of the repo's tech stack.

---

Tasks

• Investigation
  • [x] Find the easiest way to include the technology on the repo.
  • [x] Sieze alternatives to update code to Typescript API calls.
  • [x] Sieze alternatives to update code to Typescript in functions.
  • [x] Sieze alternatives to update code to Typescript in unit tests.
• Development
  • [x] Update the API's code to Typescript.
  • [x] Update the function's code to Typescript.
  • [ ] Update the unit test code for Typescript.

---

Ticket relationships

Relationship	Involved tickets
Is child of	none
In parent of	none
Is related to	none
Is blocked by	none
It blocks	none

---

Technical notes

TBD

[NicolasOmar]

Possible starting point on this link

[NicolasOmar]

Some findings that could be useful as saving-time documentation:

• These questions and their answers helped me a lot when handling interfaces for Mongoose structure models and entities.
• I continued the migration based on this article.
• After achieving a decent build, I will continue working on graphql-related file migration using Apollo's guide and some tips from stackoverflow.
• Keep in mind that if you use typescript paths in its configuration, you should add and configure ts-alias to avoid building issues.
• When you are working on unit tests, start reading Jest's documentation and integrate the tools mentioned, such as ts-jest, and start migrating test files.
  • Small note: ts-jest includes an alias mapping feature in case you add it to your repo and start having importing issues when running the test suite.