Use AuthDecorator
for instantiation of account-related AuthPayload
s
#1722
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.
Summary
When using the
AuthGuard
, we can be sure that theaccessToken
is present in therequest
. Currently, our account-related methods instantiate the relativeAuthPayload
individually. There is, however, a specific (Auth
) decorator that handles instantiation.This replaces the aforementioned for the creation, retrieval and deletion of accounts.
Changes
AuthPayload
instead ofAuthPayloadDto
inAccountsController
,AccountsService
andAccountsRepository
.AuthPayload
directly for authorisation inAccountsRepository
,