refactor: use api to store last accessed for user #3761
+71
−15
Conversation
This file contains 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
4 tasks
shreddedbacon
added
the
happy-to-delay
shreddedbacon
force-pushed
the
refactor-last-accessed-db
branch
from
a2eec19 to
ed13dde
Compare
shreddedbacon
removed
the
happy-to-delay
shreddedbacon
force-pushed
the
refactor-last-accessed-db
branch
from
ed13dde to
632a314
Compare
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.
General Checklist
Database Migrations
Saves the last user accessed time to the API DB, previous attempts stored this attribute in keycloak but encountered race conditions.
Also include the user created timestamp from keycloak.