Skip to content

ref(seer): Propagate viewer_context to replays Seer call sites#109715

Merged
azulus merged 3 commits intomasterfrom
viewer-context/replays
Mar 3, 2026
Merged

ref(seer): Propagate viewer_context to replays Seer call sites#109715
azulus merged 3 commits intomasterfrom
viewer-context/replays

Conversation

@azulus
Copy link
Member

@azulus azulus commented Mar 2, 2026

Pass SeerViewerContext to all Seer API wrapper call sites in the replays module.

PR #109697 added an optional viewer_context parameter to all Seer API wrapper functions. This PR updates the replays module call sites:

  • Endpoint (project_replay_summary): Pass both organization_id and user_id to start/state requests
  • Delete usecase (delete.py): Pass organization_id only (background task, no user context)

No behavior change — viewer_context defaults to None which preserves existing behavior.

Co-Authored-By: Claude noreply@anthropic.com

Pass SeerViewerContext to Seer API wrapper call sites in the replays
module. Endpoint has org+user context, delete usecase has org only.
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Mar 2, 2026
@azulus azulus marked this pull request as ready for review March 3, 2026 19:06
@azulus azulus requested review from a team as code owners March 3, 2026 19:06
If viewer_context contains unexpected types that orjson can't serialize,
log the error and send the request without the header rather than failing
the entire Seer API call.
@azulus azulus merged commit 3962166 into master Mar 3, 2026
78 checks passed
@azulus azulus deleted the viewer-context/replays branch March 3, 2026 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants