[Challenge]: feat: new payment flow prototype

[mariaaenc]

• You have read the CONTRIBUTING.md - File not exists
• For Terraform changes, you have read the Terraform Naming Conventions - Does not apply
• For Terraform changes, you have already executed the Terraform plan on this branch - Does not apply
• The changes inside this pull request are organization-agnostic

Why?

Challenge for Backend Software Engineer (individual-assignment)

What?

• Organize classes into specific files for their use and the files for this challenge into a new folder called typescript.
• Install jest, ts-jest and @types/jest libraries for testing and implement unit tests.
• Install prettier library for code formatting.
• Create a function to execute processes after purchase according to the rules specified in the challenge.

Jira link:

How:

• Since the process is different for each type of product, a Map was implemented that is used to redirect to the specific class that contains the processes for each product.

Comments:

Enter the correct folder: cd backend/individual-assignment/typescript
Install the libraries with the command: npm install
Script to run tests: npm run test
Script to format code: npm run format

Coverage:

[robo-bankfacil-app]

❌ Pull Request Analyzer - Failed

Hi @mariaaenc!

🚀 Analysis

✔️ Pull Request Description Approved
✔️ Pull Request Title Approved

⁉️ Actions Items

☑️ CheckList

Existem itens no checklist do pull request que não obrigatórios, por favor leia eles com atenção e conclua antes de avançar com o merge.

• ❗ You have read the CONTRIBUTING.md - File not exists
• ❗ For Terraform changes, you have read the Terraform Naming Conventions - Does not apply
• ❗ For Terraform changes, you have already executed the Terraform plan on this branch - Does not apply

---

🔑 CODEOWNERS

Não foi encontrado arquivo CODEOWNERS ou .github/CODEOWNERS no repositorio!

---

🏷️ Category

Não foi encontrado a label de categoria do Pull Request, selecione somente uma das labels abaixo:

• creditas:task:planned: Utilizada para sinalizar PR que tem origem itens planejados
• creditas:task:unplanned: Utilizado para sinalizar PR expontaneas que não estão relacionadas a atividades no board do jira
• creditas:task:emergency: Utilizado para sinalizar que é uma tarefa emergencial, como por exemplo um BOPE ou um Revert

ℹ️ Mais informações