Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Issue#301 + Issue#300 #305
base: main
Are you sure you want to change the base?
Issue#301 + Issue#300 #305
Changes from 10 commits
174d25a
f62e495
6dabc9f
398ab14
9705703
fe04636
26c762f
adcf6bf
ed52c67
514aec9
672a1ec
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Would you mind using an application properties for that
@Value
Or something similar.
For example:
findfirst.local.upload.profile-pictures=../data/uploads/profile-pictures/
findfirst.upload.location=${FINDFIRST_UPLOAD_LOCATION:${findfirst.local.upload.profile-pictures}}
Then in the docker files do something like I have for the screenshot location:
environment:
volumes:
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.
After at
@RequestParm
use the size annotation@Size(max = MAX_FILE_SIZE)
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.
Remove this because it makes it so we can not validate the user by their jwt credentials.
I would move all the internal logic from 186 - 213 into the userService.
Ideally the controller logic should mostly be handling errors if any occur, the parameters and different types of parameters then letting the Service level handle the doing.
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 would do the size check in the method parameter, also helps keep our end point from getting dsod with big files.
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.
To clear up a little bit above:
Add this to the userManagement service:
https://github.com/R-Sandor/FindFirst/blob/75ada43b5d5aa7c6ea3c808519e361e45280e5fe/server/src/main/java/dev/findfirst/core/service/BookmarkService.java#L61C1-L61C38
UserContext userContext
that allows us to get the user from the request to server rather than telling the server who you are, which could lead to me putting my photo on your profile since there is not any validation.