• Modified JwtAuthenticationFilter to add only the username of the user to the principal object

• Modified the testUser endpoint to reflect the change above

• Modified the changeUserPassword method to reflect the change above

• Fixed an antMatcher for changeUserPassword in WebSecurityConfig

Please refer to the Trello task for more details

The user now has to confirm their email address after registration.

In order to test this functionality, you need to have MailDev installed, or use a real email account and modify the properties file accordingly.

Klasa: https://github.com/Simple-as-Coding/tutoring-platform/blob/main/src/main/java/pl/simpleascoding/tutoringplatform/repository/UserRepository.java

L:9
jest: findByUsername()

powinno być:
findByUserName()

Token: -Added data field to store data like password or email -Added @Enumerated annotataion to TokenType TokenType: -Added CHANGE_EMAIL_CONFIRMATION value UserService: -Added rootUrl parametr to changeUserPassword method -Added confirmChangeUserPassword method UserServiceImpl: -Modified changeUserPassword method to sending emails -Added confirmChangeUserPassword method UserController: -Modified changeUserPassword method -Added confirmChangeUserPassword method

I've removed the Role object entirely and replaced it with a simple element collection in the user object. This is because in our implementation roles couldn't exist without a user anyway, but they would introduce a problem while fetching every user that has a specified role (please refer to a PR with teacher role implementation or ask on Discord). An element collection is, in my opinion, a better solution, because on the DB side, it creates a table that only consists of a user id and a name of the RoleType enum, and in the code we can use something like user.getRoles().contains(RoleType.TEACHER) and it will just work.

I've also implemented pagination and sorting on the api/v1/teachers/all endpoint to minimize DB load and allow for, for example, sorting the teacher list alphabetically by surname, etc.

• created Teacher DTO
• created UserIsAlreadyATeacherException exception class
• created findAllByRoleType method in RoleRepository
• created teacher controller
• created find all teachers methods in controller, facade, service and implementation
• edited role-user relation

UserService:

• Methods getUserById and getUserByUsername now return the full User object or throw an exception, as suggested by @MateuszBednarczyk

UserServiceImpl:

• Modified the code to reflect the change above
• Renamed final strings of the class to fit in with our naming convention, as suggested by @dawciobiel

• Added openapi ui path to application.properties
• Added openapi dependencies and docs
• Deleted SwaggerConfig class
• Deleted useless swagger dependencies and docs

-added link for apache-commons.md -added link for clean-code.md -added link for design-patterns.md -added link for eclipse-collections.md -added link for git.md -added link for gradle.md -added link for guava.md -added link for ide.md -added link for lombok.md -added link for maven.md -added link for postgres.md -added link for README.md

Introduced reviewing users

A review consists of a star-based rating (1-5) and an optional description (referred in the code as "content").

Everyone can see what reviews has a user received, as well as all reviews posted by the user. A review can be edited and deleted by its author. The input is validated in the controller using Spring validation, and additionally the Review entity is validated by Hibernate. The reviews are retrieved in pages of 20 elements, to avoid loading a full list of reviews at once. You can also sort the reviews by stars or creation date.

Endpoints: api/v1/reviews - POST, used to create a review api/v1/reviews/{id} - PUT, DELETE, used to modify or delete a review api/v1/users/{userId}/reviews/received - GET, used to retrieve reviews that the user has received api/v1/users/{userId}/reviews/posted - GET, used to retrieve reviews posted by the user

I'll provide a full documentation in a separate pull request.

• created getUsersAdvertisements method in controller
• created findAllByAuthor_Name method in repository
• created getUsersAdvertisements method and it's implementation