Hi 👋 ,

Thanks so much for the work on this project! At @Reviewpad, we are trying to support the OSS projects that we use as dependencies to our main repository reviewpad/reviewpad.

Do you plan to join any sponsoring program? We are also happy to help the community to maintain the project.

Thanks!

Hi!

I've changed the Mixpanel struct to be an interface and added a mock implementation in addition to the current real implementation. This makes it easy to test code which uses mixpanel:

var client mixpanel.Mixpanel = mixpanel.NewMock()

people = client.Identify("1")
people.Update("$set", map[string]interface{}{
    "custom_field": "cool!",
})

// client.People now holds the tracked data

Also, functions now only return a single error and not an HTTP response, making error handling easier.

There are cases when event tracking and user properties setting happen at the same time from different threads. But, since the map used in the mock is not thread safe, tests that use it fail unexpectedly. Using the sync.Map should solve the problem.

There are cases when event tracking and user properties setting happen at the same time from different threads. But, since the map used in the mock is not thread safe, tests that use it fail unexpectedly. Using the sync.Map should solve the problem.

Some time ago mixpanel released a new feature called "groups" (checkout: https://developer.mixpanel.com/reference/group-set-property). This PR add the ability to update such entity via this client.

In order to avoid confusion in between the mutation of Users and Groups, i deprecated the Update endpoint and renamed it UpdateUser.

The main new feature is to be able to create events older than 5 days. In order to do this, basic HTTP auth has also been added (without password as it is not required to use Import). Some other small fixes were implemented too. Mixpanel docs: https://developer.mixpanel.com/docs/importing-old-events

In short, empty Event.IP/Update.IP results in a ip=1 to be appended to the url params for people updates and events. By sending ip=1, mixpanel will automatically geolocate using the ip of the requester during the API request.

It looks like this was the intended behavior, but unfortunately it did not work as described (https://github.com/dukex/mixpanel/blob/master/mixpanel.go#L39-L40)

Hi guys.

I'm consuming the MixPanel API using this amazing library, but I'm getting a recurring issue:

*url.Error Get "https://api.mixpanel.com/engage?data=xx&ip=1": net/http: TLS handshake timeout

Can you help me with this problem, please?