This will require users to user Posthog().capture() instead of Posthog.capture()
The reason why the change is if a user wants to set the current .screen and then have that be included in future .capture events, especially where they may be calling .capture without knowing what screen the user is on. In order to do this we need to keep some state in the Posthog client and we only want one, so singleton it is!
… version v1.10.0
This will require users to user
Posthog().capture()instead ofPosthog.capture()The reason why the change is if a user wants to set the current
.screenand then have that be included in future.captureevents, especially where they may be calling.capturewithout knowing what screen the user is on. In order to do this we need to keep some state in the Posthog client and we only want one, so singleton it is!