Modify PersonalAccessToken Model to be polymorphic #49
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 PR resolves #10 .
by making PersonalAccessToken model polymorphic will allow multiple models to be authenticated through airlock tokens .
for example if i have Pharmacist & Doctor models . and would authenticate both of them through api . i would have to implement this solution which is in my opinion a little bit tedious .
but by making PersonalAccessToken model polymorphic. this will allow implementing the above use case without any extra boilerplate .
and also customization to user Model through userModel() won't be needed any more . cause polymorphic relation will support any other models .