Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Plataforma Praxi Backend Plataforma Praxi Backend
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Plataforma Praxi
  • Plataforma Praxi BackendPlataforma Praxi Backend
  • Merge requests
  • !17

Merged
Created Sep 25, 2022 by Giovane Bianchi Milani@giovane.milaniDeveloper

TypeORM error handling

  • Overview 0
  • Commits 8
  • Changes 5

Sugestão para lidarmos com alguns erros do TypeORM

Até o momento implementei o handling pra quando não acha a Resorce no banco, o Repository do TypeORM retorna um null. Eu fiz um override da funcao findOneBy da API do TypeORM pra quando achar null ele joga um NotFoundError (a nossa classe NotFoundError). Também isso evita de ficarmos fazendo verificações se entidade é nula nas Services. Se achou um nulo no banco ja retorna o erro.

Podemos usar isso pra padronizar os erros na API e evitar o retorno daqueles erros feios do TypeORM

Edited Sep 30, 2022 by Giovane Bianchi Milani
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feat/typeorm-error-handling