-
Notifications
You must be signed in to change notification settings - Fork 790
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REFACTORING] LoginController only for login flow #549
Comments
Hey slaveek, a very very good point! Thanks, I'll do this in the next days. Have a wonderful evening/day/morning :) |
Oh Yeah this is a nice Idea :D 👍 |
Yes sounds great! I did this with the user profiles on a project, too. |
Done! This is just a first preview, everything might change for sure! |
in develop branch btw |
Hi Chris BTW LoginModel looks so good now. The model directory is very clear and easy to navigate. It's extremely easy to find function that you need. Shouldn't LoginController and controller dir look similar to model? |
@slaveek Ah damn, you're right! I've indeed just cleaned the model, not the controller. Okay, ticket is open again. :) Changes will come around beginning of FEbruary. |
Okay, the changes will take a liiiittle bit longer :) |
Thanks to everybody, this is now done by slaveek's commit via #747 |
Hi.
Looking through changes in LoginController I began to think about some methods in it.
My impression is that some of the methods like:
showProfile, editUsername, uploadAvatar, changeAccountType
(all which need authentication)
are not quite related to login process.
This methods are created to do user actions after login process (edit, upload, show etc.) and don't have nothing to do with correct, safe login.
IMHO it's worth to consider in future to separate this methods in eg. UserController.
This can:
It can be a bit cleaner I think.
Just idea.
Take care.
The text was updated successfully, but these errors were encountered: