[example issue] refactor auth logic #2

Closed
opened 2025-10-16 22:13:39 +00:00 by AndreFerreira5 · 0 comments
AndreFerreira5 commented 2025-10-16 22:13:39 +00:00 (Migrated from github.com)

this is a template issue for you to follow
the authentication logic works right now, but it was written in a rush to get everything ready for production. now that we have more free time and the boss is less angry, we should refactor it and make it more robust, modular and secure. also, we could implement a new token exchange pipeline for even better security, so our db is never leaked.

this is what needs to be done:

  • separate mixed route and db logic
  • write new tests for the new logic
  • remove useless endpoint that was asked by the boss but was never really used (fuck you shit boss)
  • implement new token pipeline

you can also drop some images or attachments if they help understand the issue

we need all the help we can get, so if you are coçating your left one, come write some code, but no gpt

**_this is a template issue for you to follow_** the authentication logic works right now, but it was written in a rush to get everything ready for production. now that we have more free time and the boss is less angry, we should refactor it and make it more robust, modular and secure. also, we could implement a new token exchange pipeline for even better security, so our db is never leaked. this is what needs to be done: - [ ] separate mixed route and db logic - [ ] write new tests for the new logic - [ ] remove useless endpoint that was asked by the boss but was never really used (fuck you shit boss) - [ ] implement new token pipeline _you can also drop some images or attachments if they help understand the issue_ we need all the help we can get, so if you are coçating your left one, come write some code, but no gpt
Sign in to join this conversation.
No description provided.