You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2024. It is now read-only.
Package version is latest: "@segment/analytics-node": "^1.1.3".
The segment node package fails to send events when any of the properties attributes are of the bigint type. There's no type error, and no error returned in the callback, but the track() calls returns immediately.
I'm not quite sure what the behaviour should be here, but it took me some digging to figure out what was going on. On my app, I added a type check because I have a wrapper and use TypeScript, so now I'm covered. I think at a minimum the library should not allow bigint types, because currently the type is Record<string, any> (see https://github.com/segmentio/analytics-next/blob/master/packages/core/src/events/interfaces.ts#L22C50-L22C50), or the callback should return an error, or both.
Thanks!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Package version is latest:
"@segment/analytics-node": "^1.1.3"
.The segment node package fails to send events when any of the
properties
attributes are of thebigint
type. There's no type error, and no error returned in the callback, but thetrack()
calls returns immediately.output:
I'm not quite sure what the behaviour should be here, but it took me some digging to figure out what was going on. On my app, I added a type check because I have a wrapper and use TypeScript, so now I'm covered. I think at a minimum the library should not allow
bigint
types, because currently the type isRecord<string, any>
(see https://github.com/segmentio/analytics-next/blob/master/packages/core/src/events/interfaces.ts#L22C50-L22C50), or the callback should return an error, or both.Thanks!
The text was updated successfully, but these errors were encountered: