feat(profile): implement profile picture and cv routes #44
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This implements the functions in the
profileservice to store attachments (profile picture, CV) to a profile. The following methods were implemented to be used through the message broker:findOneCvOfUser: gets the CV of a user, corresponds to theGET /profile/cvAPI routesaveOneCvOfUser: sets the CV of a user, corresponds to thePOST /profile/cvAPI routefindOneProfilePictureOfUser: gets the profile picture of a user, corresponds to theGET /profile/photoAPI routesaveOneProfilePictureOfUser: sets the profile picture of a user, corresponds to thePOST /profile/photoAPI routeThe attachments are stored in an S3-compatible object storage that can be configured in the
profileservice configuration.