feat: add lastAccessed
key to track user login
#364
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.
Problem
This PR adds a new
lastAccessed
key in theUser
collection which gets updated every time the user's document is retrieved when the user logs into the application.This PR also adds a new
updatedAt
key which is only updated when contact is updated for now. Thetimestamp
plugin is not used as updating thelastAccessed
key will also inadvertently update theupdatedAt
key, which is not the behaviour we want.Closes #345
Solution
Features:
lastAccessed
andupdatedAt
keys to User model which gets updated when user logins and when new user is created/user updates their contact respectively.