chore: Update all_users.json to include last_active_at & last_sign_in_at fields #41
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
…_at fields - last_sign_in_at stores the last time of a user's successful sign-in - last_active_at stores the latest date with session activity with day precision
gkats
approved these changes
Dec 5, 2023
dimkl
approved these changes
Dec 6, 2023
georgepsarakis
deleted the
georgepsarakis-CORE-960-users-last-active-at
branch
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.
Updating the fixture to display the current available fields for a User resource and their format:
last_sign_in_atstores the last time of a user's successful sign-inlast_active_atstores the latest date with session activity with day precision