Sundayjob996 - #74
Merged
Merged
Conversation
GET /api/v1/feed/subscriptions returns an aggregated, cursor-paginated timeline of posts from a fan's actively-subscribed creators. Scoped via an INNER JOIN against subscriptions (not a creatorId IN-list) so the query plan stays index-driven regardless of how many creators a fan follows; supports all/media/text filtering, opaque base64 cursors with stable publishedAt+id ordering, and rejects malformed cursors as 400 VALIDATION_ERROR. Adds a feed-specific posts index, docs/feed.md, and unit + e2e test coverage.
GdprService referenced AuditAction.GDPR_DATA_EXPORTED and USER_SELF_DELETED, which didn't exist on the enum — this broke `npm run build` on main independent of the feed work, which would have kept CI red regardless of the feed feature's correctness.
4 tasks
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
2 participants
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.
closes #58
Implemented the core Fan Feed API with efficient cursor-based pagination and strict content visibility rules.
What was implemented
GET /api/v1/feed/subscriptionsendpoint for authenticated fans.{ data, nextCursor, hasMore }response format.all,media, andtextfilters.publicandsubscribersposts accessible to the fan.publishedAt DESC, id DESC.{ publishedAt, id }) for pagination.IN (...)queries.