Auth Controller Structure & Error Handling
I am trying to replace the old login/register controllers in my asp.net web api portfolio project because most of it consists of "if" statements with very little separation of concerns.
I'm asking claude/chatgpt for some ideas for me to learn from to make a professional looking controller, and it's showing me this ExecuteAuthFlow method in a base controller (top) for error handling, and an AuthService for things such as user validation in the login controller (bottom) that inherits from the base controller.
I'm wondering if this is the right direction for my portfolio project with how an auth system should be made?
I'm asking claude/chatgpt for some ideas for me to learn from to make a professional looking controller, and it's showing me this ExecuteAuthFlow method in a base controller (top) for error handling, and an AuthService for things such as user validation in the login controller (bottom) that inherits from the base controller.
I'm wondering if this is the right direction for my portfolio project with how an auth system should be made?
