Introduction of libhoney.Client should be documented in changelog

[BRMatt]

This commit changed beeline.Init() so that it doesn't call the global libhoney.Init. This broke some of our services that are using both libhoney events and beeline traces while they migrate to libhoney.

Please can you document this change in the changelog?

[maplebed]

Yes! Thank you; that should have happened in the first place.

[maplebed]

Erp. Updating that changelog felt awfully familiar... The changes are already pending in an existing not-yet-reviewed PR #52

I'll bump the review request and get it merged.

[maplebed]

I updated the changelog in b76b6f0 but it occurs to me that perhaps some more text around the libhoney.Client change would be useful to help people understand the ramifications of the change. (As an example, the problem you ran in to would not be obvious from what's currently written there.)

Do you have any suggestions on the type of language that would be useful there? Maybe something like this?

This change means that the beeline no longer uses the global libhoney config. If you are setting specific configurations on the global libhoney and wish them to be used by the beeline, you will need to create a libhoney client with those changes and explicitly configure the beeline with that client.

[BRMatt]

That sounds like a great idea! It might be worth saying that this would affect folks who are manually calling libhoney.Init() in addition to beeline.Init(), as folks who didn't setup the library might not be sure how a "global libhoney config" relates to the code they have in front of them.

[JamieDanielson]

Closing this as there has been no recent activity and it appears it was covered in changelog updates. Feel free to request a re-open if it’s still relevant.