feat: add last_active_at column and POST /v1/users/me/ping endpoint#953
Merged
Conversation
Adds a `last_active_at` timestamptz column to the users table and a new authenticated endpoint that upserts it on each app-open. This replaces plays-based inactivity detection with a direct activity signal. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The g.Use("/users/:userId") prefix middleware was matching POST
/users/me/ping (with :userId="me"), causing a 400 before the ping
handler could run.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
last_active_attimestamp column to theuserstable (migration 0221)POST /v1/users/me/pingendpoint that updateslast_active_atfor the authenticated userg.Use("/users/:userId")prefix middleware was catching/users/me/ping(with:userId="me") and returning 400 before the ping handler could run — the middleware now passes through when:userIdis the literal "me"Test plan
POST /v1/users/me/pingreturns{"status": "ok"}for authenticated requestslast_active_atis updated in the DB after a ping/users/:userIdroutes still resolve user IDs correctlyGET /users/<invalid_id>still returns 400🤖 Generated with Claude Code