-
Notifications
You must be signed in to change notification settings - Fork 937
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
implemented methods dedicated to user logging in #1145
base: master
Are you sure you want to change the base?
Changes from 2 commits
89231d6
ffc6cba
cded22b
cc72766
b6b40cd
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,7 @@ | ||
package mate.academy.service; | ||
|
||
import mate.academy.model.User; | ||
|
||
public class AuthenticationService { | ||
/** | ||
* Imagine that some user wants to login to your site. | ||
|
@@ -11,6 +13,11 @@ public class AuthenticationService { | |
* Return false in any other cases. | ||
*/ | ||
public boolean login(String email, String password) { | ||
UserService userService = new UserService(); | ||
User user = userService.findByEmail(email); | ||
if (user != null) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. you can use ternary operator here There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i tried something like this |
||
return (user.getPassword().equals(password)) ? true : false; | ||
} | ||
return false; | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's make UserService class-level variable to avoid creating this object each time you call login method
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. I thought that since Java take care of automatically destruction of object (because it doesn't have explicitly defined destructors) - it would be right to create this object inside of method, just to renew users datarecords each time when method is called. Second reason - what will happen if between method calls to the User will be added new authentication records...