Repository navigation
fix(devvit): harden payment readiness contracts - #74
Conversation
|
Warning Review limit reached
Next review available in: 36 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughDevvit commerce installation now fails closed after target availability is applied. Target-artifact smoke checks validate payment permissions, products, and internal endpoints. Platform order timestamp validation now rejects impossible UTC dates and accepts valid whole-second UTC timestamps. ChangesDevvit validation
Platform order validation
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant verifyDevvitWebManifest
participant assertDevvitPaymentsReadiness
participant verifyEnabledDevvitPayments
verifyDevvitWebManifest->>assertDevvitPaymentsReadiness: validate effective config and payment permission
assertDevvitPaymentsReadiness-->>verifyDevvitWebManifest: return enabled product SKUs
verifyDevvitWebManifest->>verifyEnabledDevvitPayments: validate products and internal endpoints
verifyEnabledDevvitPayments-->>verifyDevvitWebManifest: complete manifest checks
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 381f58fcf0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| assertBooleanValue( | ||
| features.iap, | ||
| permissionEnabled, | ||
| `${label} effective target config features.iap`, |
There was a problem hiding this comment.
Allow non-payment Devvit targets to smoke
When smoking the repository's default reddit target, apps/target-devvit/devvit.json still has permissions.payments set to false while packages/target-config/targets.json keeps reddit.features.iap and reddit.monetization.iap set to true. This new equality check makes verifyTargetArtifacts reject that default no-payments Devvit manifest before it considers whether any effective products are enabled, so pnpm build:devvit && pnpm smoke:target reddit and generated games that have not enabled Devvit payments will fail. Either align the default config/manifest or only require the payments permission when enabled effective SKUs are exposed.
Useful? React with 👍 / 👎.
Summary
Follow-up to the actionable review findings on #73.
Validation
pnpm test:target-artifactspnpm --filter @mpgd/adapter-devvit testpnpm --filter @mpgd/adapter-devvit checkpnpm --filter @mpgd/game-services testpnpm --filter @mpgd/game-services checkpnpm checkadapter-devvitandgame-services0.8.1; dependency propagation tocliandcreate-game0.10.1)Summary by CodeRabbit
Bug Fixes
Tests