Refactor/auth architecture pt 1

[Dan-Y-Ko]

Description

This pr covers moving the login logic to the modules folder and using DI to call the adapter in the UI. Expected behavior is the user will get redirected and you can see the refresh token and access token cookies in the browser.

This is just a part of the entire auth architecture refactor process. I didn't want to make the pr too big. Some of the file organization will be messy, ignore that. It will all eventually get fixed.

IMPORTANT: in this pr, only the login functionality works, nothing else.

Issue link

Fixes # (issue)

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [X] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

• [X] My code follows the style guidelines of this project
• [X] I have performed a self-review of my code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [X] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes
• [X] Any dependent changes have been merged and published in downstream modules

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
chingu-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 17, 2024 8:51pm