feat(engagement): add manual refresh RPC + dashboard e2e test (#175)#235
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.
Expose public.refresh_post_engagement_daily() (SECURITY DEFINER, guarded by is_manager()) so the dashboard can be refreshed on demand — the materialized view lives in the
privateschema and was not reachable from a client. It refreshes non-concurrently because PostgREST wraps each request in a transaction; the hourly pg_cron job keeps using CONCURRENTLY.Add the DoD's end-to-end test: seed sessions, refresh manually and assert the numbers the screen consumes, covering engagement_sessions → materialized view → public view → listPostEngagement(), plus RBAC.
Closes #175