Document UIKit customPaywallTraits handling; fix stale API names#38
Document UIKit customPaywallTraits handling; fix stale API names#38salami wants to merge 1 commit into
Conversation
- Add a collapsible section under Embedded View explaining how customPaywallTraits are snapshotted at display and how to keep them current when hosting HeliumPaywall in UIKit via UIHostingController (ObservableObject pattern). - Fix stale HeliumPaywallView -> HeliumPaywall in the embedded example. - Fix stale HeliumPurchaseDelegate -> HeliumPaywallDelegate in the iOS quickstart (matches the actual protocol name in the SDK). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 47 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: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
1 participant
Summary
Docs updates alongside helium-swift #296 (trait-staleness follow-ups).
customPaywallTraitsare snapshotted at display and fixed for the presentation, that SwiftUI keeps them current automatically when they come from re-rendering state, and shows theObservableObject+UIHostingControllerpattern for keeping them current before display. This is the target of the new SDK docstring link (#embedded-view).HeliumPaywallView→HeliumPaywallin the embedded example (the type isHeliumPaywall).HeliumPurchaseDelegate→HeliumPaywallDelegatein the iOS quickstart — matches the actual protocol name in the SDK (HeliumPaywallDelegate).🤖 Generated with Claude Code
Note
Low Risk
Markdown-only documentation changes with no runtime, security, or data impact.
Overview
Documentation-only updates for iOS paywall integration, aligned with helium-swift trait-staleness follow-ups.
Under iOS → Embedded View in the paywall presentation guide, a new accordion explains that
customPaywallTraitsare snapshotted at display and stay fixed for that presentation. It contrasts SwiftUI (traits from re-rendering state stay current) with UIKit +UIHostingController, and documents anObservableObject/PaywallTraitsStorepattern so fresh traits reachHeliumPaywallviaPaywallPresentationConfigbefore the paywall is shown — with a note that updates after display do not change an already-visible paywall.Stale API names are corrected:
HeliumPaywallView→HeliumPaywallin the embeddedPaywallEventHandlersexample, andHeliumPurchaseDelegate→HeliumPaywallDelegatein the iOS quickstart custom purchase section.Reviewed by Cursor Bugbot for commit 8a31adb. Bugbot is set up for automated code reviews on this repo. Configure here.