feat(engagement): track-engagement Edge Function with batch upsert (#179)#228
Merged
Merged
Conversation
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.
Rewrite the Edge Function to accept event batches (array or { events: [] }), validate with zod, authenticate via JWT, and delegate to a new apply_engagement_events RPC (append-only link_clicked, status transition, focused_seconds accumulation, max_scroll_pct max, per-post pre-aggregation). Conform the trackLinkClick client to the array contract. Add pgTAP + real-DB integration tests, the endpoint README, and allow console in edge functions.
Closes #179