#429: Implement GET /subscription_user Endpoint #580
Merged
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.
Issue link / number:
#429
What changes did you make?
I created DTOs to define the structure of what will be sent/exchanged.
GetSubscriptionUserDto
GetSubscriptionUsersDto
I created a method in the
SubscriptionUserService
that returns all the subscriptions by a user id.I created a method in the
SubscriptionUserController
that gets the authenticated user from the request. I used thereq['UserEntity]
instead ofreq['user']
because I seen in other issues that this will be the main way to retrieve the user. I then formatted the response to adhere to the requested structure in the issue.Why did you make the changes?
The application wants to separate the users subscriptions from the
/user/me
endpoint, that way the client can request this/api/v1/subscription-user/subscription_user
as needed to only retrieve the subscriptions.Did you run tests?
I created and ran 2 unit tests in the existing subscription-user.spec.ts (Passing).