-
Notifications
You must be signed in to change notification settings - Fork 0
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
9-feature-1-user-registration #17
base: main
Are you sure you want to change the base?
Conversation
…sues that remain are related to persistance, sometimes the accounts are not saved, other times they are.
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.
I review These classes/interfaces UserVerifier, UserVerificationUI, UserRegUseCase and UserRegistrationUI. I haven't found any issues, and they are following the clean architecture. Nice job!
If I want to add a recommendation, I suggest using different packages to organize user classes. (i.e. for example, a package for tests, interfaces and entities)it makes it easier to follow your codes.
…e" into an object that would either send the code via phone number or email
…possible to add multiple users to the file without issues
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.
nice work , no issues found , ready to merge to main .
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.
the developer choose clear names for variables, classese, method. And the code is well-designed and appropiate for our application
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.
I think the code is well implemented with clean architectures. You implemented Entities, Usecases and UIs. I think it is also great that you have implemented a lot of test cases to make sure your code work as expected. Good Job! One thing that you could consider is maybe to add some more edge cases to your tests, such as cases with empty strings.
@@ -89,14 +90,6 @@ public List<User> getList() { | |||
ObjectInputStream in = new ObjectInputStream(fileIn)) { | |||
|
|||
users = (ArrayList<User>) in.readObject(); | |||
/* | |||
while(true){ |
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.
I think it is correct to delete this while loop since it is not necessary
src/test/java/UserDatabaseTest.java
Outdated
UserDatabase accountDatabase = new UserDatabase(accounts); | ||
accountDatabase.createUser("MeenakshiGopakumar", "123", "[email protected]", "Basic"); | ||
List<User> lst = accountDatabase.getList(); | ||
String email = lst.get(0).getEmail(); | ||
System.out.println(email); | ||
Assertions.assertTrue(email.equals("[email protected]")); | ||
} | ||
|
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.
Maybe we can do another test with edge cases that contains empty informations (e.g. "" for email)
a6d0b75
No description provided.