Closed silesky closed 4 months ago
Latest commit: 33464cd00170ad7915825a81340a0fc3dc31ea3f
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
This addresses an inconsistency with analytics-node (new vs old).
There are cases valid use cases where we want the messageId to be overridable, such as deduping.
This ensures backward compatibility with analytics-node by modifying '@segment/analytics-core'. Specifically, the changes prevent the generation of a messageId if it is already set. This adjustment aligns with the behavior outlined in analytics-node's source code here.
While this is a core release, only the node library is affected, as the browser has its own EventFactory atm.