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
User service #38
User service #38
Conversation
moustaphastar
commented
Sep 28, 2021
- Implemented new endpoints and objects in order
- to get a paged list of users
- to get a single user
- delete a user
- Added access rule for delete and list endpoints
- Implemented user page, details modal and api request for admin panel.
Create user (#31 ) implementation is missing. |
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.
CreateUser (#31) missing.
|
||
|
||
const columns = [ | ||
"id", "Ad", "Email", "Telefon", "Lokasyon", "İşlemler" |
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.
What columns to show/hide?
path: "/api/v1/file", | ||
data: formData, | ||
params: ["firebasePath"], | ||
values: ["product-images"] |
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.
Value should be user-image
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.
Also, do we have the implementation to add a user image?
|
||
@Override | ||
public UserImageInsertResponse insertUserImage(UserImageInsertRequest request) { | ||
return new UserImageInsertResponse(); |
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.
User image insertion is done through FileResource
endpoints.
public ResponseEntity<PageResponse<UserResponse>> pageList( | ||
@RequestParam("page") int page, | ||
@RequestParam("size") int size) { | ||
Authentication auth = SecurityContextHolder.getContext().getAuthentication(); |
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.
Can we refactor to use hasRole
or hasAuthority
annotations?
@Mapping(target = "revisedAt", | ||
dateFormat = "dd-MM-yyyy HH:mm:ss") | ||
UserResponse entityToUserResponse(UserEntity entity); | ||
|
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.
We don't need target attribute for entity properties that has same name with response property
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.
Reviewed.