fix(posthog): 'history_change' as a capture_pageview option#620
fix(posthog): 'history_change' as a capture_pageview option#620
Conversation
|
@zizzfizzix is attempting to deploy a commit to the Nuxt Team on Vercel. A member of the Team first needs to authorize it. |
📝 WalkthroughWalkthroughThis change extends the Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
commit: |
|
Thanks 😊 |
🔗 Linked issue
❓ Type of change
📚 Description
For SPAs (most Nuxt apps) when the user wants pageview events captured they need to pass
history_changeas the option to posthog.Without nuxt/scripts accepting this, a user would have to resort to using the config param and pass raw options instead, despite this being a native one.
See posthog docs, here