events: add GET /v1/events/:eventId/followers#774
Merged
dylanjeffers merged 1 commit intomainfrom Apr 21, 2026
Merged
Conversation
New read endpoint returning the users subscribed to a remix-contest event, ordered by each follower's own follower count so the most- followed fans surface first. Shape mirrors /v1/users/:userId/followers so the same User renderers consume it. Filters mirror the existing follow_state semantics: - entity_type='Event' only (ignores legacy 'User' rows with colliding numeric ids) - is_current & NOT is_delete - is_deactivated excluded The subscriptions table reuses `user_id` as the mirrored event id, so a plain USING(user_id) join against users / aggregate_user is ambiguous — joins are qualified against subscriber_id instead. Feeds the web Followers card's avatar stack + leaderboard chevron. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
New read endpoint returning the users subscribed to a remix-contest event, ordered by each follower's own follower count so the most- followed fans surface first. Shape mirrors /v1/users/:userId/followers so the same User renderers consume it.
Filters mirror the existing follow_state semantics:
The subscriptions table reuses
user_idas the mirrored event id, so a plain USING(user_id) join against users / aggregate_user is ambiguous — joins are qualified against subscriber_id instead.Feeds the web Followers card's avatar stack + leaderboard chevron.