feat: google stale prisma #8642

mikeallisonJS · 2026-01-27T02:14:16Z

Summary by CodeRabbit

New Features
- Added OAuth state tracking to better manage authorization refresh failures and require re-authorization when necessary.
Bug Fixes
- Improved handling of OAuth token refresh by automatically clearing the stale authorization flag upon successful updates.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

…Spaces types This update introduces the oauthStale field to the IntegrationGoogle and IntegrationGrowthSpaces types in the GraphQL schema, indicating whether OAuth credentials are stale. Additionally, the field is integrated into the relevant resolvers and service logic to manage OAuth token refresh states effectively.

This update introduces the StaleOAuthError class to manage scenarios where Google integration OAuth credentials are stale, requiring re-authorization. The error is integrated into the getTeamGoogleAccessToken and getIntegrationGoogleAccessToken functions, preventing token refresh attempts when the integration is marked as stale. Additionally, the appendEventToGoogleSheets function is updated to skip syncing silently when a StaleOAuthError is encountered.

…stale-google-integration

…logic This update removes the StaleOAuthError class and its associated handling from the Google authentication functions. The logic for marking integrations as stale and throwing errors has been eliminated, simplifying the getTeamGoogleAccessToken and getIntegrationGoogleAccessToken functions. The appendEventToGoogleSheets function has also been adjusted to directly retrieve the access token without handling stale integration scenarios.

coderabbitai · 2026-01-27T02:14:48Z

Walkthrough

A new oauthStale boolean field is added to the Integration model with a default value of false. The database schema, migration, and Google integration update mutation are updated to support this field, which tracks OAuth token refresh failures. Test fixtures are updated to include the new field.

Changes

Cohort / File(s)	Summary
Schema & Database `libs/prisma/journeys/db/schema.prisma`, `libs/prisma/journeys/db/migrations/20260119200000_add_oauth_stale_to_integration/migration.sql`	Added new `oauthStale Boolean` @default`(false)` field to Integration model; created SQL migration to add the column to the database table.
Google Integration Update `apis/api-journeys-modern/src/schema/integration/google/googleUpdate.mutation.ts`, `apis/api-journeys-modern/src/schema/integration/google/googleUpdate.mutation.spec.ts`	Updated mutation to set `oauthStale: false` in the update payload when refreshing Google integration; test updated with matching field.
Test Fixtures `apis/api-journeys/src/app/modules/integration/growthSpaces/growthSpaces.resolver.spec.ts`, `apis/api-journeys/src/app/modules/integration/growthSpaces/growthSpaces.service.spec.ts`, `libs/yoga/src/crypto/crypto.spec.ts`	Added `oauthStale: false` field to Integration test objects.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

feat: add google auth integration to backend #8310: Modifies the Google integration update flow and Integration schema; both PRs update the googleUpdate mutation and Prisma Integration model.

Suggested reviewers

tanflem

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'feat: google stale prisma' is vague and doesn't clearly convey the purpose of the changes. While it mentions 'google' and 'stale' and 'prisma', it lacks specificity about what is being added or why the oauthStale field is being introduced.	Consider a more descriptive title such as 'feat: add oauthStale field to Integration model' or 'feat: track OAuth token staleness in Google integration' that clearly explains the feature being added.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch 00-00-MA-feat-google-stale-prisma

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

nx-cloud · 2026-01-27T02:15:32Z

View your CI Pipeline Execution ↗ for commit e3d6924

Command	Status	Duration	Result
`nx run watch-e2e:e2e`	✅ Succeeded	18s	View ↗
`nx run journeys-admin-e2e:e2e`	✅ Succeeded	39s	View ↗
`nx run resources-e2e:e2e`	✅ Succeeded	13s	View ↗
`nx run short-links-e2e:e2e`	✅ Succeeded	3s	View ↗
`nx run player-e2e:e2e`	✅ Succeeded	3s	View ↗
`nx run videos-admin-e2e:e2e`	✅ Succeeded	4s	View ↗
`nx run-many --target=vercel-alias --projects=jo...`	✅ Succeeded	2s	View ↗
`nx run-many --target=vercel-alias --projects=re...`	✅ Succeeded	2s	View ↗
`Additional runs (16)`	✅ Succeeded	...	View ↗

☁️ Nx Cloud last updated this comment at 2026-01-27 20:32:54 UTC

github-actions · 2026-01-27T02:21:40Z